Skip to content
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

Azure Blueprint Artifact Update #2594

Closed
bashscr opened this issue Oct 30, 2020 · 6 comments · Fixed by #2679
Closed

Azure Blueprint Artifact Update #2594

bashscr opened this issue Oct 30, 2020 · 6 comments · Fixed by #2679
Assignees
Labels
Blueprint question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@bashscr
Copy link

bashscr commented Oct 30, 2020

Hi,

Going through the Azure CLI for using the Blueprint module, I see that you can add a --depends-on to a specific artifact. However, the CLI doesn't seem to support removing this property or setting it to be empty: []. When you try to set the artifact's "dependsOn" property to empty or "", it gives an error when trying to publish the new blueprint. The only way to fix this, that I have found so far, is by exporting the entire Blueprint with artifacts using Powershell and removing the "dependsOn" property manually inside of the artifact file. Then publishing a new version works as expected.

Is there any documentation to direct me in the right direction? I can't seem to find anything, and I would prefer to use the Azure CLI if possible rather than having to use both. Thank you!

V/r


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 30, 2020
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Nov 2, 2020
@yungezz
Copy link
Member

yungezz commented Nov 2, 2020

hi @fengzhou-msft could you pls help to look at the issue? thanks

@bashscr
Copy link
Author

bashscr commented Nov 24, 2020

Hi, I just wanted to check back in @yungezz @fengzhou-msft with both of you. I see a new issue has been created and awaiting a merge. I'm glad to see the progress here. Additionally, I would like to inquire about being able to export the blueprint and artifacts from the Azure CLI like you can with Export-AzBlueprintWithArtifact. Is there any plans for this? We are trying to keep consistency and use the Azure CLI as much as possible, and would prefer not to rely on having to install PowerShell modules for other users if we can do everything through the Azure CLI. Thanks.

@yungezz
Copy link
Member

yungezz commented Nov 25, 2020

thanks for the feedback @bashscr . Linked PR will merged soon after reviewing finished. To export the blueprint and artifacts, do you mind to create a new issue to track the request so that we can planning it accordingly? thanks.

@bashscr
Copy link
Author

bashscr commented Nov 25, 2020

thanks for the feedback @bashscr . Linked PR will merged soon after reviewing finished. To export the blueprint and artifacts, do you mind to create a new issue to track the request so that we can planning it accordingly? thanks.

Sure thing, and thank you @yungezz I just made a new issue here: Export Blueprints

@fengzhou-msft
Copy link
Member

@bashscr blueprint 0.2.1 is released. Now you should be able to remove the dependency with --depends-on appending no values in update commands.

@bashscr
Copy link
Author

bashscr commented Nov 26, 2020

Can confirm everything is working from my end, thanks a lot! @fengzhou-msft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blueprint question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants