-
Notifications
You must be signed in to change notification settings - Fork 428
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
[Bug]: Error: failed to find allowed user domains, err = object does not exist #2927
Comments
Hey @nicolamarangoni. Thanks for reaching out to us. Please share the config and the DEBUG logs. |
This is our config:
|
Adding something like |
Thanks! cc: @sfc-gh-jmichalak |
Hi @nicolamarangoni 👋 We're assuming that we get user domains from Snowflake describe, but for some reason it's probably missing here. Can you check that |
Hi @sfc-gh-jmichalak ALLOWED_USER_DOMAINS is not listed. |
Same here. We also cannot downgrade as the database resource has been upgraded and we are getting the error:
|
@gbatiz @nicolamarangoni Thanks for your feedback, this is undocumented Snowflake behavior and we're investigating it internally. |
@gbatiz Until we know if this is a Snowflake issue or intentional undocumented behavior, you can use provider alias for the saml resource (so that only saml resource works on the previous version but you use the newest for the databases and all other objects). |
@sfc-gh-asawicki Reading the docs, I am not sure how to do this, if possible. Version is not something the providers aliases can differ on. Do you have a working example of this that you are comfortable sharing by any chance? |
I don't have a working solution share, but this is a bit tricky solution, so after giving it a second, maybe we shouldn't have recommended it. Still, the alternative would be to split into different deployments but this is a more time-consuming solution. We are investigating internally the encountered behavior; as a last resort, we will provide a workaround in v0.94.0. |
Thanks! For now we commented out the code for the resource and removed it from terraform state. Once the issue is resolved, we import it back. |
<!-- Feel free to delete comments as you fill this in --> - add a state upgrader to set `default` for affected resources - add an entry the in migration guide with explanation of the issue (also add a warning for v0.93) - add sdk validation for setting conflicting values - add resource validation for setting conflicting values in create/update (can't do it as ValidateFunc because it has scope of only one field) - add acceptance tests to cover flow with this issue - improve docs for other security integrations ## Test Plan <!-- detail ways in which this PR has been tested or needs to be tested --> * [x] acceptance tests <!-- add more below if you think they are relevant --> * [x] unit tests ## References <!-- issues documentation links, etc --> References #2946, #2927.
@gbatiz @nicolamarangoni This has been fixed in v0.94. Please follow our migration guide. When this field is missing from the output, instead of failing the whole operation, now it's only logged. |
Closing as completed. Please open a new one if the error persists in the newest provider version. |
Terraform CLI Version
1.9.2
Terraform Provider Version
0.93
Terraform Configuration
Category
category:resource
Object type(s)
No response
Expected Behavior
After align resources with new 0.93 standards, the plan should be successful.
Actual Behavior
The resource snowflake_saml2_integration fails with the below message message.
Reverting to snowflake_saml_integration doesn't help. I get the same error.
Steps to Reproduce
Upgrade provider to 0.93 with a deployment containing snowflake_saml2_integration.
How much impact is this issue causing?
High
Logs
No response
Additional Information
No response
Would you like to implement a fix?
The text was updated successfully, but these errors were encountered: