-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding patching scenario ARM API #25446
Adding patching scenario ARM API #25446
Conversation
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Validation Report
|
compared tags (via openapi-validator v2.1.4) | new version | base version |
---|---|---|
package-preview-2023-08 | package-preview-2023-08(87c9398) | package-preview-2023-08(release-app-Microsoft.App-2023-08-01-preview) |
[must fix]The following errors/warnings are introduced by current PR:
Rule | Message | Related RPC [For API reviewers] |
---|---|---|
Based on the response model schema, operation 'Patches_ListByBuilderResource' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.App/preview/2023-08-01-preview/Patches.json#L37 |
||
OperationId should contain the verb: 'skipconfig' in:'Patches_Skip_Configure'. Consider updating the operationId Location: Microsoft.App/preview/2023-08-01-preview/Patches.json#L191 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️
Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Swagger Validation Report
|
Rule | Message |
---|---|
unacceptable kind of an object to dump [object Error] |
"role":"Model Validation", "url":"https://github.com/Azure/azure-rest-api-specs/blob/79b9e8e4a7bf51a26f6852f2dd8af11703157416/specification/app/resource-manager/Microsoft.App/preview/2023-08-01-preview/Patches.json" |
unacceptable kind of an object to dump [object Error] |
"role":"Model Validation", "url":"https://github.com/Azure/azure-rest-api-specs/blob/79b9e8e4a7bf51a26f6852f2dd8af11703157416/specification/app/resource-manager/Microsoft.App/preview/2023-08-01-preview/Patches.json" |
️❌
SemanticValidation: 2 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
OBJECT_ADDITIONAL_PROPERTIES |
Additional properties not allowed: nullable JsonUrl: Microsoft.App/preview/2023-08-01-preview/Patches.json#L356:21 |
INVALID_TYPE |
Expected type object but found type string JsonUrl: Microsoft.App/preview/2023-08-01-preview/Patches.json#L356:21 |
️❌
PrettierCheck: 6 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
HowToFix |
Code style issues found path: Microsoft.App/preview/2023-08-01-preview/Patches.json |
HowToFix |
Code style issues found path: preview/2023-08-01-preview/examples/Patches_Apply.json |
HowToFix |
Code style issues found path: preview/2023-08-01-preview/examples/Patches_Delete.json |
HowToFix |
Code style issues found path: preview/2023-08-01-preview/examples/Patches_Get.json |
HowToFix |
Code style issues found path: preview/2023-08-01-preview/examples/Patches_ListByBuilderResource.json |
HowToFix |
Code style issues found path: preview/2023-08-01-preview/examples/Patches_Skip_Configure.json |
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️⌛
PR Summary pending [Detail]
️⌛
Automated merging requirements met pending [Detail]
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
This PR is currently trying to merge into another person's feature branch. The idea here is to minimize the file diff shown so that we won't have duplicate reviews on the same files. The changes will be merged into |
} | ||
} | ||
}, | ||
"/subscription/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/patches/{patchName}/skip/{patchSkipConfig}": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"/subscription/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/patches/{patchName}/skip
This path doesn't align with the guidelines.
Can this be -
"/subscription/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/patches/{patchName}/skipConfig ? #Resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Adding this change in the next commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't see a change here. POST URLs must end with the action name (skipConfig) on a resource ({patchName}). They can't be a parameter like you have here. The URL in sjanamma's comment above is correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I might get confused about that a bit. The parameter is now changed to an in-body one to make sure the path for post action aligns with the guideline.
"description": "Patching operation has been started.", | ||
"schema": { | ||
"$ref": "#/definitions/PatchResource" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
202 response can't have response body, it should return empty body. #Resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it! updated in the latest commit
} | ||
}, | ||
"204": { | ||
"description": "Patch deletion completed successfully." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated in the latest commit.
} | ||
}, | ||
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/patches/{patchName}": { | ||
"get": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going through earlier comments and observed that there is only get and delete on patches resource type. and you explained that patch resource is created when a build instance is being created.
Does that mean, there will be only one patch resource that can be created under a build resource instance? More like singleton instance? #Resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There could be multiple patch resources created. And by patch resources, I mean the db entries that user interacts. If there are multiple container apps created in an environment, and many of them are available to be patched, then there could be multiple patch resources.
"description": "The status of the patch operation once it has been provisioned", | ||
"readOnly": true | ||
}, | ||
"createdTime": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There’s already createTime and UpdateTime inside commontype/proxyResource/systemdata
And Patch resource contains proxyResource
"description": "Container App Patch",
"allOf": [
{
"$ref": "../../../../../common-types/resource-management/v3/types.json#/definitions/ProxyResource"
}
]
It‘s dup createTime and updateTime here in my opinion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the main reason we have a createdTime here is because the systemData created time is not used in patches. The resource created time we have shows the resource creation time in data plane. Updated time shows the last time the resource got updated either by user or data plane.
I believe this is also what container app revision was doing.
One more question about this API - is this really best modeled as a POST API? It sounds to me a bit like either it is 'creating' an instance of a skip configuration for an existing patch, which I imagine is something that should be gettable later, or 'updating' a patch, by adding a skip config on it. Do either of these match your mental model? In which case it seems like it could have been modeled with different verbs/actions such as and in the former case, skip configs could be created using templates, blocked using policy, etc. Do you still think POST is preferable? "/subscription/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.App/builders/{builderName}/patches/{patchName}/skipConfig": { |
Thanks for double checking! I still think that POST method lines up with the current design of patches more then the other methods. For skipping a patch, instead of creating a policy for it to be skipped, it is actually updating a field called And for PATCH method, because skipping is not fully customizing the patch object, I don't want to give the impression that the patch object could be updated by user in anyways. Therefore, I used post/delete method to define skipping, deleting and applying. And these methods are the only "actions" that the user could use to interact with patch resource. |
/pr RequestMerge |
c70291e
into
release-app-Microsoft.App-2023-08-01-preview
* Adds base for updating Microsoft.App from version preview/2023-05-02-preview to version 2023-08-01-preview * Updates readme * Updates API version in new specs and examples * Add type to Certificate (#25380) * Add type to Certificate * lint * Add gpus property to AvailableWorkloadProfiles. (#25328) * Add gpus property to AvailableWorkloadProfiles. * Fix. * Pauld/re add build and builder (#25442) * cherry picked the build and builder updates * some more cleanup * added arm id format, removed extra properties, and named the resource provisioning states * Add OT and AI config (#25350) * Add OT and AI config * resolve comments * Add service bind properties to dapr component (#25781) * dapr component sb-bind definition add * fix * ran npx prettier * npx prettier --------- Co-authored-by: [email protected] <[email protected]> * Adding patching scenario ARM API (#25446) * cherry picked the build and builder updates * some more cleanup * Adding patching scenario and samples * Added to readme * Lint fix * Linting * Linting error fix * Addressed comments and added extra properties * Linting * Fixing patch skip post action * Linting * Addressing comments * Reverting patchDetails changes * Fixing pipeline error * Linting * Removed invalid required tag * Fixed examples * Addressed comments --------- Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> * Update microsoft.app 2023-08-01-preview for new DaprSubscription API feature (#25631) * ACA Dapr Subscription: WIP Signed-off-by: Bernd Verst <[email protected]> * Add Dapr Subscription examples Signed-off-by: Bernd Verst <[email protected]> * complete examples Signed-off-by: Bernd Verst <[email protected]> * Add DaprSubscription descriptions Signed-off-by: Bernd Verst <[email protected]> * include updated readme Signed-off-by: Bernd Verst <[email protected]> * fix casing Signed-off-by: Bernd Verst <[email protected]> * formatting Signed-off-by: Bernd Verst <[email protected]> * Use Types v5 Signed-off-by: Bernd Verst <[email protected]> * Revert "Use Types v5" v5 causes several mysterious SDK build errors in this branch on this PR. To avoid this error we will stick to v3 for now. We will upgrade to v5 in a future net new branch. This reverts commit 6a43aac. --------- Signed-off-by: Bernd Verst <[email protected]> * Support log streaming on build resource (#25902) * updated the build resource to support build upload and log streaming, with a token to be passed in via header * add x-ms-secret and update buildendpoint -> endpoint * retrieve log stream and upload endpoint tokens through post requests, as they are secrets * remove secret flag from tokenendpoint property, as we expect users to retrieve it * rename file * updated format of how build object returns auth token * fix example * added expiration date to token response * fix auth token to also include build resource information * renamed getAuthToken -> listAuthToken and removed resource information from token response * fix examples * updated samples to be more accurate * Update serviceBinds with clientType and customizedKeys (#26111) * Update serviceBinds with clientType and customizedKeys * force ci * fix missing } --------- Co-authored-by: Ahmed ElSayed <[email protected]> * Adds new Dapr Component Resiliency Feature to existing version `Release app microsoft.app 2023 08 01 preview` (#26107) * Add Dapr Component Resiliency Policies APIs to ContainerApps 2023-08-01-preview Signed-off-by: Bernd Verst <[email protected]> * Update deletion return code * Fix variable name * Remove invalid status code from example * prettify * Register new resource in readme * Remove existing import cycle * Use integers not integer strings * Fix delete status codes * More changes * Update examples * Revert "Remove existing import cycle" which causes unrelated failures This reverts commit 8ce1a74. --------- Signed-off-by: Bernd Verst <[email protected]> * Add API spec for ContainerApp Resiliency (#25732) Signed-off-by: Hal Spang <[email protected]> * Add extendedlocation for job (#26196) * Add extendedlocation for job * Add sample for container apps on connectedEnvironment * Fixes for examples * Fix connected environment example * Update old examples * removing SourceToCloud patching from 08-01-preview (#26245) * Add diagnostic routes to Container App Jobs (#26227) * Add diagnostic routes to Container App Jobs * Update * Update * Update * Update * Update * Update * Update operationIds --------- Co-authored-by: Michimune Kohno <[email protected]> * Update app resiliency rest api spec (#26357) Signed-off-by: Yash Nisar <[email protected]> * Fix ACA component resiliency examples (#26441) * Fix arm review comments for container app (#26455) * update * update * update * Fix SDK build error for Microsoft.App (#26416) * Fix SDK build error for Microsoft.App * Update * update * update * update --------- Co-authored-by: Michimune Kohno <[email protected]> * Fix arm review comments for container app (#26479) * fix * update * update * Fix detectorProperties request path (#26431) * fix list exception * change param to enum * fix lint error * revert not working changes * fix enum * rearrange --------- Co-authored-by: Chenghui Yu <[email protected]> * Enable dynamicJsonColumns for log analytics configuration (#26432) * Enable dynamicJsonColumn for log analysis configuration * Add missed s * Fix code style * Update container app usages value to float (#26448) * update * update * update * Fix App Resiliency retry example (#26560) Signed-off-by: Yash Nisar <[email protected]> * Fix lint warning for container app (#26523) * fix warning * fix warning * upate --------- Signed-off-by: Bernd Verst <[email protected]> Signed-off-by: Hal Spang <[email protected]> Signed-off-by: Yash Nisar <[email protected]> Co-authored-by: zhenqxuMSFT <[email protected]> Co-authored-by: yalixiang <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Michael Dai <[email protected]> Co-authored-by: bgashirabake <[email protected]> Co-authored-by: [email protected] <[email protected]> Co-authored-by: Harry Li <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Bernd Verst <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: halspang <[email protected]> Co-authored-by: LaylaLiu-gmail <[email protected]> Co-authored-by: michimune <[email protected]> Co-authored-by: Michimune Kohno <[email protected]> Co-authored-by: Yash Nisar <[email protected]> Co-authored-by: Seris370 <[email protected]> Co-authored-by: Chenghui Yu <[email protected]>
* Adds base for updating Microsoft.App from version preview/2023-05-02-preview to version 2023-08-01-preview * Updates readme * Updates API version in new specs and examples * Add type to Certificate (#25380) * Add type to Certificate * lint * Add gpus property to AvailableWorkloadProfiles. (#25328) * Add gpus property to AvailableWorkloadProfiles. * Fix. * Pauld/re add build and builder (#25442) * cherry picked the build and builder updates * some more cleanup * added arm id format, removed extra properties, and named the resource provisioning states * Add OT and AI config (#25350) * Add OT and AI config * resolve comments * Add service bind properties to dapr component (#25781) * dapr component sb-bind definition add * fix * ran npx prettier * npx prettier --------- Co-authored-by: [email protected] <[email protected]> * Adding patching scenario ARM API (#25446) * cherry picked the build and builder updates * some more cleanup * Adding patching scenario and samples * Added to readme * Lint fix * Linting * Linting error fix * Addressed comments and added extra properties * Linting * Fixing patch skip post action * Linting * Addressing comments * Reverting patchDetails changes * Fixing pipeline error * Linting * Removed invalid required tag * Fixed examples * Addressed comments --------- Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> * Update microsoft.app 2023-08-01-preview for new DaprSubscription API feature (#25631) * ACA Dapr Subscription: WIP Signed-off-by: Bernd Verst <[email protected]> * Add Dapr Subscription examples Signed-off-by: Bernd Verst <[email protected]> * complete examples Signed-off-by: Bernd Verst <[email protected]> * Add DaprSubscription descriptions Signed-off-by: Bernd Verst <[email protected]> * include updated readme Signed-off-by: Bernd Verst <[email protected]> * fix casing Signed-off-by: Bernd Verst <[email protected]> * formatting Signed-off-by: Bernd Verst <[email protected]> * Use Types v5 Signed-off-by: Bernd Verst <[email protected]> * Revert "Use Types v5" v5 causes several mysterious SDK build errors in this branch on this PR. To avoid this error we will stick to v3 for now. We will upgrade to v5 in a future net new branch. This reverts commit 6a43aac. --------- Signed-off-by: Bernd Verst <[email protected]> * Support log streaming on build resource (#25902) * updated the build resource to support build upload and log streaming, with a token to be passed in via header * add x-ms-secret and update buildendpoint -> endpoint * retrieve log stream and upload endpoint tokens through post requests, as they are secrets * remove secret flag from tokenendpoint property, as we expect users to retrieve it * rename file * updated format of how build object returns auth token * fix example * added expiration date to token response * fix auth token to also include build resource information * renamed getAuthToken -> listAuthToken and removed resource information from token response * fix examples * updated samples to be more accurate * Update serviceBinds with clientType and customizedKeys (#26111) * Update serviceBinds with clientType and customizedKeys * force ci * fix missing } --------- Co-authored-by: Ahmed ElSayed <[email protected]> * Adds new Dapr Component Resiliency Feature to existing version `Release app microsoft.app 2023 08 01 preview` (#26107) * Add Dapr Component Resiliency Policies APIs to ContainerApps 2023-08-01-preview Signed-off-by: Bernd Verst <[email protected]> * Update deletion return code * Fix variable name * Remove invalid status code from example * prettify * Register new resource in readme * Remove existing import cycle * Use integers not integer strings * Fix delete status codes * More changes * Update examples * Revert "Remove existing import cycle" which causes unrelated failures This reverts commit 8ce1a74. --------- Signed-off-by: Bernd Verst <[email protected]> * Add API spec for ContainerApp Resiliency (#25732) Signed-off-by: Hal Spang <[email protected]> * Add extendedlocation for job (#26196) * Add extendedlocation for job * Add sample for container apps on connectedEnvironment * Fixes for examples * Fix connected environment example * Update old examples * removing SourceToCloud patching from 08-01-preview (#26245) * Add diagnostic routes to Container App Jobs (#26227) * Add diagnostic routes to Container App Jobs * Update * Update * Update * Update * Update * Update * Update operationIds --------- Co-authored-by: Michimune Kohno <[email protected]> * Update app resiliency rest api spec (#26357) Signed-off-by: Yash Nisar <[email protected]> * Fix ACA component resiliency examples (#26441) * Fix arm review comments for container app (#26455) * update * update * update * Fix SDK build error for Microsoft.App (#26416) * Fix SDK build error for Microsoft.App * Update * update * update * update --------- Co-authored-by: Michimune Kohno <[email protected]> * Fix arm review comments for container app (#26479) * fix * update * update * Fix detectorProperties request path (#26431) * fix list exception * change param to enum * fix lint error * revert not working changes * fix enum * rearrange --------- Co-authored-by: Chenghui Yu <[email protected]> * Enable dynamicJsonColumns for log analytics configuration (#26432) * Enable dynamicJsonColumn for log analysis configuration * Add missed s * Fix code style * Update container app usages value to float (#26448) * update * update * update * Fix App Resiliency retry example (#26560) Signed-off-by: Yash Nisar <[email protected]> * Fix lint warning for container app (#26523) * fix warning * fix warning * upate * update tests for jobs * update tests for jobs * fix name and resource values in examples * fix name and resource values in examples * fix name and resource values in examples * fix name and resource values in examples --------- Signed-off-by: Bernd Verst <[email protected]> Signed-off-by: Hal Spang <[email protected]> Signed-off-by: Yash Nisar <[email protected]> Co-authored-by: Zunli Hu <[email protected]> Co-authored-by: zhenqxuMSFT <[email protected]> Co-authored-by: yalixiang <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Michael Dai <[email protected]> Co-authored-by: bgashirabake <[email protected]> Co-authored-by: [email protected] <[email protected]> Co-authored-by: Harry Li <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Bernd Verst <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: halspang <[email protected]> Co-authored-by: LaylaLiu-gmail <[email protected]> Co-authored-by: michimune <[email protected]> Co-authored-by: Michimune Kohno <[email protected]> Co-authored-by: Yash Nisar <[email protected]> Co-authored-by: Seris370 <[email protected]> Co-authored-by: Chenghui Yu <[email protected]>
* Adds base for updating Microsoft.App from version preview/2023-05-02-preview to version 2023-08-01-preview * Updates readme * Updates API version in new specs and examples * Add type to Certificate (#25380) * Add type to Certificate * lint * Add gpus property to AvailableWorkloadProfiles. (#25328) * Add gpus property to AvailableWorkloadProfiles. * Fix. * Pauld/re add build and builder (#25442) * cherry picked the build and builder updates * some more cleanup * added arm id format, removed extra properties, and named the resource provisioning states * Add OT and AI config (#25350) * Add OT and AI config * resolve comments * Add service bind properties to dapr component (#25781) * dapr component sb-bind definition add * fix * ran npx prettier * npx prettier --------- Co-authored-by: [email protected] <[email protected]> * Adding patching scenario ARM API (#25446) * cherry picked the build and builder updates * some more cleanup * Adding patching scenario and samples * Added to readme * Lint fix * Linting * Linting error fix * Addressed comments and added extra properties * Linting * Fixing patch skip post action * Linting * Addressing comments * Reverting patchDetails changes * Fixing pipeline error * Linting * Removed invalid required tag * Fixed examples * Addressed comments --------- Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> * Update microsoft.app 2023-08-01-preview for new DaprSubscription API feature (#25631) * ACA Dapr Subscription: WIP Signed-off-by: Bernd Verst <[email protected]> * Add Dapr Subscription examples Signed-off-by: Bernd Verst <[email protected]> * complete examples Signed-off-by: Bernd Verst <[email protected]> * Add DaprSubscription descriptions Signed-off-by: Bernd Verst <[email protected]> * include updated readme Signed-off-by: Bernd Verst <[email protected]> * fix casing Signed-off-by: Bernd Verst <[email protected]> * formatting Signed-off-by: Bernd Verst <[email protected]> * Use Types v5 Signed-off-by: Bernd Verst <[email protected]> * Revert "Use Types v5" v5 causes several mysterious SDK build errors in this branch on this PR. To avoid this error we will stick to v3 for now. We will upgrade to v5 in a future net new branch. This reverts commit 6a43aac. --------- Signed-off-by: Bernd Verst <[email protected]> * Support log streaming on build resource (#25902) * updated the build resource to support build upload and log streaming, with a token to be passed in via header * add x-ms-secret and update buildendpoint -> endpoint * retrieve log stream and upload endpoint tokens through post requests, as they are secrets * remove secret flag from tokenendpoint property, as we expect users to retrieve it * rename file * updated format of how build object returns auth token * fix example * added expiration date to token response * fix auth token to also include build resource information * renamed getAuthToken -> listAuthToken and removed resource information from token response * fix examples * updated samples to be more accurate * Update serviceBinds with clientType and customizedKeys (#26111) * Update serviceBinds with clientType and customizedKeys * force ci * fix missing } --------- Co-authored-by: Ahmed ElSayed <[email protected]> * Adds new Dapr Component Resiliency Feature to existing version `Release app microsoft.app 2023 08 01 preview` (#26107) * Add Dapr Component Resiliency Policies APIs to ContainerApps 2023-08-01-preview Signed-off-by: Bernd Verst <[email protected]> * Update deletion return code * Fix variable name * Remove invalid status code from example * prettify * Register new resource in readme * Remove existing import cycle * Use integers not integer strings * Fix delete status codes * More changes * Update examples * Revert "Remove existing import cycle" which causes unrelated failures This reverts commit 8ce1a74. --------- Signed-off-by: Bernd Verst <[email protected]> * Add API spec for ContainerApp Resiliency (#25732) Signed-off-by: Hal Spang <[email protected]> * Add extendedlocation for job (#26196) * Add extendedlocation for job * Add sample for container apps on connectedEnvironment * Fixes for examples * Fix connected environment example * Update old examples * removing SourceToCloud patching from 08-01-preview (#26245) * Add diagnostic routes to Container App Jobs (#26227) * Add diagnostic routes to Container App Jobs * Update * Update * Update * Update * Update * Update * Update operationIds --------- Co-authored-by: Michimune Kohno <[email protected]> * Update app resiliency rest api spec (#26357) Signed-off-by: Yash Nisar <[email protected]> * Fix ACA component resiliency examples (#26441) * Fix arm review comments for container app (#26455) * update * update * update * Fix SDK build error for Microsoft.App (#26416) * Fix SDK build error for Microsoft.App * Update * update * update * update --------- Co-authored-by: Michimune Kohno <[email protected]> * Fix arm review comments for container app (#26479) * fix * update * update * Fix detectorProperties request path (#26431) * fix list exception * change param to enum * fix lint error * revert not working changes * fix enum * rearrange --------- Co-authored-by: Chenghui Yu <[email protected]> * Enable dynamicJsonColumns for log analytics configuration (#26432) * Enable dynamicJsonColumn for log analysis configuration * Add missed s * Fix code style * Update container app usages value to float (#26448) * update * update * update * Fix App Resiliency retry example (#26560) Signed-off-by: Yash Nisar <[email protected]> * Fix lint warning for container app (#26523) * fix warning * fix warning * upate --------- Signed-off-by: Bernd Verst <[email protected]> Signed-off-by: Hal Spang <[email protected]> Signed-off-by: Yash Nisar <[email protected]> Co-authored-by: zhenqxuMSFT <[email protected]> Co-authored-by: yalixiang <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Michael Dai <[email protected]> Co-authored-by: bgashirabake <[email protected]> Co-authored-by: [email protected] <[email protected]> Co-authored-by: Harry Li <[email protected]> Co-authored-by: Paul Dorsch <[email protected]> Co-authored-by: Bernd Verst <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: Ahmed ElSayed <[email protected]> Co-authored-by: halspang <[email protected]> Co-authored-by: LaylaLiu-gmail <[email protected]> Co-authored-by: michimune <[email protected]> Co-authored-by: Michimune Kohno <[email protected]> Co-authored-by: Yash Nisar <[email protected]> Co-authored-by: Seris370 <[email protected]> Co-authored-by: Chenghui Yu <[email protected]>
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequested
is removed from your PR. This should cause the label
WaitForARMFeedback
to be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see
Getting help
section below.Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReview
label.Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help
and https://aka.ms/ci-fix.