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

Allow key rotations without destroying SAMLv2 IDP resources #269

Closed
wants to merge 1 commit into from

Conversation

sjauld
Copy link
Contributor

@sjauld sjauld commented Apr 22, 2024

Resolves #268

@mmanes
Copy link
Contributor

mmanes commented May 17, 2024

ForceNew was intentionally added to this field in 37d66a7. @robotdan Do you have any context on why that was done?

@sjauld
Copy link
Contributor Author

sjauld commented May 17, 2024

#135 references this as well

@edmeister
Copy link

This obvious bug is one of the things that are currently blocking us from using continuing the use the Terraform provider. Can we somehow poke a maintainer to merge this in? I've tried through our enterprise support, but with little success.

@sjauld
Copy link
Contributor Author

sjauld commented May 21, 2024

@edmeister looks like this will be in the next release per #275

@mmanes
Copy link
Contributor

mmanes commented May 24, 2024

Thanks! This change has been released as part of https://github.com/FusionAuth/terraform-provider-fusionauth/releases/tag/v0.1.106.

@mmanes mmanes closed this May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Certificate rotation causes recreation of fusionauth_idp_saml_v2 resource
3 participants