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

[Bug Report]: bicep publish script #4113

Open
demargkhrab opened this issue Oct 20, 2023 · 0 comments
Open

[Bug Report]: bicep publish script #4113

demargkhrab opened this issue Oct 20, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@demargkhrab
Copy link

demargkhrab commented Oct 20, 2023

Describe the bug

following this page to publish modules manually.

i get bicep publish is not a valid command error, the scrip does a "bicep publish" and not an "az bicep publish" .... there seems to be no reference to bicep publish anymore.

To reproduce

when i load the script and run the commands as per the setup page ... this is the example below which is fine, have added the paths in here.

$modules = Get-ChildItem -Path 'c:\repos\resourcemodules' -Recurse -Filter 'main.bicep'
$modules.FullName | ForEach-Object -Parallel {
   . 'c:\repos\resourcemodules\utilities\pipelines\resourcepublish\Publish-ModuleToPrivateBicepRegistry.ps1'
   Publish-ModuleToPrivateBicepRegistry -TemplateFilePath $_ -ModuleVersion '<moduleVersion>' -BicepRegistryName '<registryName>' -BicepRegistryRgName '<bicepRGName>'
} -ThrottleLimit 4

im on azcli 2.53.0
bicep cli version 0.22.6

i got around this by updating the publish function in the script to be az bicep publish -- file .... then keep the rest of the path as is ....

you also have to use az login and not Connect-AzAccount.

Code snippet

No response

Relevant log output

No response

@demargkhrab demargkhrab added the bug Something isn't working label Oct 20, 2023
@github-project-automation github-project-automation bot moved this to Needs triage in Bug board Oct 20, 2023
@AlexanderSehr AlexanderSehr added this to the Azure Verfified Modules (AVM) - CI Issues milestone May 19, 2024
@AlexanderSehr AlexanderSehr removed this from the Azure Verfified Modules (AVM) - CI Issues milestone Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Needs triage
Development

No branches or pull requests

2 participants