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

r/subnet: switching over the association resources #5801

Merged
merged 7 commits into from
Feb 18, 2020

Conversation

tombuildsstuff
Copy link
Contributor

This PR removes the network_security_group_id and route_table_id fields from the azurerm_subnet resource in favour of the split-out association resources.

It also goes through and updates the tests to confirm that delta updates are correctly handled for these resources - which were previously handled in the route table resource (but needed to be moved to the association resource)

Fixes #3302
Fixes #3749
Fixes #4818

@tombuildsstuff
Copy link
Contributor Author

Tests pass:

Screenshot 2020-02-18 at 12 36 09

@tombuildsstuff
Copy link
Contributor Author

The broken website Travis is complaining about has been fixed via #5807 - so this should be fine

Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

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

LGTM

@tombuildsstuff tombuildsstuff merged commit 15f05be into master Feb 18, 2020
@tombuildsstuff tombuildsstuff deleted the f/subnet-deprecation branch February 18, 2020 18:50
tombuildsstuff added a commit that referenced this pull request Feb 18, 2020
@ghost
Copy link

ghost commented Feb 24, 2020

This has been released in version 2.0.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.0.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.