fix: SCIM access token compatible identifiers #750
Merged
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
This reverts commit d25048a.
|
/ok-to-test sha=7477bb6 |
|
Integration tests success for 7477bb6 |
alldoami
approved these changes
Nov 9, 2021
daniepett
pushed a commit
to daniepett/terraform-provider-snowflake
that referenced
this pull request
Feb 9, 2022
This was referenced Nov 1, 2022
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.
Currently the GENERATE_SCIM_ACCESS_TOKEN fails because the results column is in lowercase when QUOTED_IDENTIFIER_IGNORE_CASE = TRUE is on account level. Solution would be to use UPPERCASE for the column so that the success of this function is not dependent on the QUOTED_IDENTIFIER_IGNORE_CASE parameter
Relates to #729
Test Plan
References