Introduce ExactVersion property for Platform an GalleryImages #7911
Conversation
This file contains 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
|
Azure Pipelines successfully started running 1 pipeline(s). |
soshekar
changed the title
|
Azure Pipelines successfully started running 1 pipeline(s). |
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-go - Release
|
soshekar
changed the title
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Dec 6, 2019
hyonholee
approved these changes
Dec 6, 2019
yungezz
reviewed
Dec 10, 2019
| @@ -6962,6 +6962,11 @@ | |||
| "version": { | |||
| "type": "string", | |||
| "description": "Specifies the version of the platform image or marketplace image used to create the virtual machine. The allowed formats are Major.Minor.Build or 'latest'. Major, Minor, and Build are decimal numbers. Specify 'latest' to use the latest version of an image available at deploy time. Even if you use 'latest', the VM image will not automatically update after deploy time even if a new version becomes available." | |||
| }, | |||
| "exactVersion": { | |||
There was a problem hiding this comment.
is there any user impact since this changed a stable version?
There was a problem hiding this comment.
for VMScaleSet VMs, there was only 1 field 'version' returning the decimal version before. Now this new field returns the decimal version. the existing 'version' could return either 'latest' or decimal values of the version ( depending on what the user passed. ). CRP is already following this behavior. To be precise, we have now made the VMScaleSet VM behavior consistent with regular VM behavior.
There was a problem hiding this comment.
thanks for explanataion. So this change will not be breaking change to customers of this stable version via rest api, SDks, CLIs, right?
|
Can one of the admins verify this patch? |
|
ping for update |
|
hi @soshekar is this PR ready to merge? thanks. |
|
ping again for confirmation, will merge it after confirm. |
yungezz
approved these changes
Jan 3, 2020
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.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.