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

Update azurerm_policy_set_definition: Make metadata Computed to avoid some unexpected diff #6266

Merged
merged 1 commit into from
Mar 30, 2020

Conversation

ArcturusZhang
Copy link
Contributor

The field metadata may return some values from the service after creation (for instance, time created on, etc), therefore it should be Computed: true like the metadata in azurerm_policy_definition.

@ghost ghost added the size/XS label Mar 26, 2020
@katbyte katbyte added this to the v2.4.0 milestone Mar 30, 2020
@katbyte katbyte merged commit ec9174b into hashicorp:master Mar 30, 2020
katbyte added a commit that referenced this pull request Mar 30, 2020
@ArcturusZhang ArcturusZhang deleted the fix-policy-set-definition branch March 30, 2020 02:54
@ghost
Copy link

ghost commented Apr 2, 2020

This has been released in version 2.4.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.4.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Apr 29, 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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants