Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Fix default subnet prefixes #73

Merged
merged 3 commits into from
Oct 14, 2022

Conversation

lonegunmanb
Copy link
Member

@lonegunmanb lonegunmanb commented Oct 14, 2022

Since we've added CI pipeline to this module a lot of files have been changed, so I'd like to re-write #57 based on the latest master branch. Thanks @diogomaul for your contribution.

This pr will fix #61

@lonegunmanb lonegunmanb temporarily deployed to acctests October 14, 2022 06:48 Inactive
Copy link
Collaborator

@jiaweitao001 jiaweitao001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM, thanks. I have one question commented underneath.

provider "azurerm" {
features {
resource_group {
prevent_deletion_if_contains_resources = false
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any specific reason we set this to false?

Copy link
Member Author

@lonegunmanb lonegunmanb Oct 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In some test environments, there might be some Azure Policy that would add extra network security groups and rules to enforce shift-right security and compliance, that could break our tests. To make sure that these tests are stable at anytime anywhere, I set this argument to false.

@lonegunmanb lonegunmanb merged commit b6eb38b into Azure:master Oct 14, 2022
@lonegunmanb lonegunmanb deleted the fix-default-subnet-prefixes branch October 14, 2022 08:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The default number of subnet prefixes should be 3
2 participants