Microsoft.ContainerInstance : Updated API version 2024-05-01-preview for ContainerGroupProfile feature#30694
Merged
drishtipeshwani09 merged 16 commits intoAzure:mainfrom Sep 26, 2024
Conversation
… profile and the corresponding examples
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Generated ApiView
|
This was referenced Sep 23, 2024
… name and removed LRO tag
…rishtipeshwani09/azure-rest-api-specs into dpeshwani/cgProfiletolatestAPI
This was referenced Sep 23, 2024
…or cg profile revisions
kaushik-ms
approved these changes
Sep 24, 2024
…tainer group profile name
…rishtipeshwani09/azure-rest-api-specs into dpeshwani/cgProfiletolatestAPI
…rishtipeshwani09/azure-rest-api-specs into dpeshwani/cgProfiletolatestAPI
|
Azure Pipelines successfully started running 3 pipeline(s). |
...source-manager/Microsoft.ContainerInstance/preview/2024-05-01-preview/containerInstance.json
Show resolved
Hide resolved
| }, | ||
| { | ||
| "$ref": "#/parameters/ResourceGroupNameParameter" | ||
| } |
Contributor
There was a problem hiding this comment.
Same as above. #Resolved
Member
Author
There was a problem hiding this comment.
Thank you for the suggestion!! I have replaced all the standard parameter references (SubId, ResourceGroupName, ApiVersion, Location) to directly use the one's present in common-types
...source-manager/Microsoft.ContainerInstance/preview/2024-05-01-preview/containerInstance.json
Show resolved
Hide resolved
…irectly from the common-types
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
Your branch is out-of-date with base branch, please merge with base branch before requesting merge. |
ms-bogdan-rotaru
approved these changes
Sep 26, 2024
cheukchuen
pushed a commit
that referenced
this pull request
Jan 24, 2025
…for ContainerGroupProfile feature (#30694) * Added the container group profile model , api paths related to the cg profile and the corresponding examples * Modifed cg profile properties struction, added pattern for cg profile name and removed LRO tag * Modified files names for better context and removed deregister path for cg profile revisions * Updated container group profiles patch path and added pattern for container group profile name * Updated the file name * Replaced all the standard parameter references in order to use them directly from the common-types * Corrected the relative path * Updated the sub id parameter to a uuid format
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. 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 the diagram Step 2, "ARM API changes review", for this PR.
Additional information
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 ApiViewcomment 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
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.