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

Removed forceNew flag from resource_service_principal tags #245

Merged
merged 5 commits into from
May 14, 2020
Merged

Removed forceNew flag from resource_service_principal tags #245

merged 5 commits into from
May 14, 2020

Conversation

MarkDordoy
Copy link
Contributor

You can update a service principal's tags without destroy it using the graph API or powershell, so there is no reason why this provider should force a new Service Principal

@ghost ghost added the size/XS label Apr 28, 2020
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

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

Thanks for the pr @MarkDordoy, this just needed tags to be added to the update function which i've done, hope you don't mind 🙂 LGTM now!

@katbyte katbyte added this to the v0.9.0 milestone May 14, 2020
@katbyte katbyte merged commit d52535a into hashicorp:master May 14, 2020
katbyte added a commit that referenced this pull request May 14, 2020
@ghost
Copy link

ghost commented May 15, 2020

This has been released in version 0.9.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 "azuread" {
    version = "~> 0.9.0"
}
# ... other configuration ...

@MarkDordoy MarkDordoy deleted the md/support-tag-update-without-destroy branch May 15, 2020 16:55
@ghost
Copy link

ghost commented Jun 13, 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 Jun 13, 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