fix: Use correct spelling for XmlSigKeyInfoKeyNameTransformer
#614
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrparkers
approved these changes
Oct 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that the
resource.keycloak_saml_identity_provider.xml_sign_key_info_key_name_transformerattribute wasn't taking effect in the Keycloak Admin Console and discovered that this is actually because the property is spelled wrong in the Terraform provider's JSON payload. I think this affects both OIDC and SAML.Provider key:
xmlSignKeyInfoKeyNameTransformer(see here)Keycloak key:
xmlSigKeyInfoKeyNameTransformer(notice theSigwithoutn, see here for example)This is the easiest and most backwards compatible fix I could think of, I hope it's okay.