-
Notifications
You must be signed in to change notification settings - Fork 377
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
[AVM Module Issue]: avm/ptn/lz/sub-vending: Re-running tries to delete a subnet (and possibly more) #3330
Comments
@cspring86, thanks for submitting this issue for the Important A member of the @Azure/avm-ptn-lz-subvending-module-owners-bicep or @Azure/avm-ptn-lz-subvending-module-contributors-bicep team will review it soon! |
Please switch to the latest version where we have updated the network resource API which overcomes the problem of rebuilding the subnets. |
@sebassem I've upgraded to 0.1.4 and I'm still getting the error. It's in the "lz-vend-vnet-create-[random]" deployment.
|
Hey @cspring86, Could you share an example module declaration and the values you are setting for this deployment? **Please redact any sensitive information 👍 ** Myself & @sebassem can then look further into this #RR |
@jtracey93 sure, here you go.
Let me know if you need anything else. |
@cspring86 Thanks Chris, we have identified the problem and a PR is on the way |
Amazing, thanks @sebassem ! |
@sebassem Unrelated to this issue, but I've just tried to create a new subscription using 0.1.4 version (the upgrade you requested as part of this issue) of the If I downgrade to 0.1.2 (my previous version), it works. The error also happens in 0.1.3. Is this a known issue or shall I raise another issue here? |
Hi @cspring86 , this is a current issue in Azure and on the way to be resolved. Once it's resolved I will submit the PR for this GitHub issue |
## Description Bump the LZ virtual network resource to avoid subnet deletion on PUT requests Fixes #3330 <!-- >Thank you for your contribution ! > Please include a summary of the change and which issue is fixed. > Please also include the context. > List any dependencies that are required for this change. --> ## Pipeline Reference <!-- Insert your Pipeline Status Badge below --> | Pipeline | | -------- | | [![avm.ptn.lz.sub-vending](https://github.com/sebassem/bicep-registry-modules/actions/workflows/avm.ptn.lz.sub-vending.yml/badge.svg?branch=avm-ptn-sub-vending-network-api)](https://github.com/sebassem/bicep-registry-modules/actions/workflows/avm.ptn.lz.sub-vending.yml) | ## Type of Change <!-- Use the checkboxes [x] on the options that are relevant. --> - [ ] Update to CI Environment or utilities (Non-module affecting changes) - [ ] Azure Verified Module updates: - [X] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in `version.json`: - [X] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description. - [ ] The bug was found by the module author, and no one has opened an issue to report it yet. - [ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in `version.json`. - [ ] Breaking changes and I have bumped the MAJOR version in `version.json`. - [ ] Update to documentation ## Checklist - [X] I'm sure there are no other open Pull Requests for the same update/change - [X] I have run `Set-AVMModule` locally to generate the supporting module files. - [X] My corresponding pipelines / checks run clean and green without any errors or warnings <!-- Please keep up to date with the contribution guide at https://aka.ms/avm/contribute/bicep -->
Check for previous/existing GitHub issues
Issue Type?
I'm not sure
Module Name
avm/ptn/lz/sub-vending
(Optional) Module Version
0.1.2
Description
I've got an Azure subscription vending repository using Bicep and Azure DevOps pipelines to manage the creation, update and cancelling of Azure subscriptions.
I'm using the
avm/ptn/lz/sub-vending
module to handle the subscription creation/update part of the process.I've created a subscription using the module, which went fine.
Another team has then proceeded to populate the VNet with subnets and other resources, as expected. One of these resources is an AKS cluster.
I've since re-run the pipeline to update the same subscription by enabling more resource providers in the
avm/ptn/lz/sub-vending
module configuration and it fails trying to delete one of the subnets.The bottom-most error message in a nested stack of messages is this:
Is this expected behaviour?
I thought Bicep ran in incremental mode by default, not complete mode, so it shouldn't be attempting to delete anything.
I need the
avm/ptn/lz/sub-vending
module to be able to create and update subscriptions when needed, such that it only updates the configuration/resources that it owns. I don't want it to interfere with resources created outside of it.(Optional) Correlation Id
No response
The text was updated successfully, but these errors were encountered: