PATCH /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/?api-version=2023-08-01-preview

Update a BuilderResource

Servers

Path parameters

Name Type Required Description
subscriptionId String Yes

The ID of the target subscription. The value must be an UUID.

builderName String Yes

The name of the builder.

resourceGroupName String Yes

The name of the resource group. The name is case insensitive.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
properties Object No

The updatable properties of the BuilderResource.

properties.environmentId String No

Resource ID of the container apps environment that the builder is associated with.

tags Object No

Resource tags.

identity Object No

Managed service identity (system assigned and/or user assigned identities)

identity.tenantId String No

The tenant ID of the system assigned identity. This property will only be provided for a system assigned identity.

identity.type String Yes

Type of managed service identity (where both SystemAssigned and UserAssigned types are allowed).

Possible values:

  • "SystemAssigned"
  • "SystemAssigned,UserAssigned"
  • "UserAssigned"
  • "None"
identity.userAssignedIdentities Object No

The set of user assigned identities associated with the resource. The userAssignedIdentities dictionary keys will be ARM resource ids in the form: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}. The dictionary values can be empty objects ({}) in requests.

identity.principalId String No

The service principal ID of the system assigned identity. This property will only be provided for a system assigned identity.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.