[Compute] vm create: Add a local copy of image alias file so that it can be accessed in a restricted network environment #10852
Conversation
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
Member
Author
|
@haroldrandom We can cooperate to use CI to update this file up to date. But not urgent. This file is very stable. |
Member
Author
|
@fengzhou-msft Do you know how to involve a resource file into project? |
Collaborator
|
@haroldrandom please help with this PR. |
fengzhou-msft
approved these changes
Oct 29, 2019
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Issue #4611
Environment like Azure GOV can't access Internet other than servers of Azure. When creating VM, Azure CLI visit a image alias file in Github to translate image alias to full urn. This patch intends to add a local copy of this file as a backup in case of network issue.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).
I adhere to the Command Guidelines.