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]: ACR version 0 already exists. #3339

Closed
mpr555 opened this issue Jun 15, 2023 · 1 comment · Fixed by #3388
Closed

[Bug Report]: ACR version 0 already exists. #3339

mpr555 opened this issue Jun 15, 2023 · 1 comment · Fixed by #3388
Assignees
Labels
bug Something isn't working

Comments

@mpr555
Copy link

mpr555 commented Jun 15, 2023

Describe the bug

After the initial creation of the module in azure container registry it errors when trying to push to version 0. It wants a --force flag on it.

it does create a new number and push that.

To reproduce

updated a module in my own project in Azure DevOps. Imported yesterday fresh from this main github repo.

Code snippet

No response

Relevant log output

VERBOSE: Performing the operation "Publish" on target "Private bicep registry entry [bicep/modules/compute.galleries.images] version [0] to registry [xxx]".
The module "br:xxx/bicep/modules/compute.galleries.images:0" already exists in registry. Use --force to overwrite the existing module.
VERBOSE: Publish complete
##[error]Script failed with exit code: 1
/usr/bin/az account clear
Finishing: Publish module to private bicep registry
@mpr555 mpr555 added the bug Something isn't working label Jun 15, 2023
@rahalan
Copy link
Contributor

rahalan commented Jun 22, 2023

Needs investigation

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: Closed
Development

Successfully merging a pull request may close this issue.

3 participants