-
Notifications
You must be signed in to change notification settings - Fork 427
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]: Terraform fails to success while creating secure procedure in reader account though procedure gets created in account. #2993
Comments
Also |
Hi @hnmpatel 👋 It seems like you are not authorized to do a |
@sfc-gh-jmichalak Is it possible that, role can create procedure but do not have permission to describe? If we have to grant separate grants then could you please give reference? |
I see that you're using a separate reader account for reading procedures, right? It seems like show operation is not permitted (docs), so maybe it affects describe operation as well? Please check on your reader account to see if you can run show and describe procedures. If it's not possible, then it's just a Snowflake limitation, and I would advise using a regular account for this resource. |
@hnmpatel did you have a chance to verify what @sfc-gh-jmichalak suggested? |
Yeah the show and describe are not possible in the reader account hence I had to use null resources for that. |
Okay, thanks! So I understand that because this is a Snowflake limitation, we can close this issue? |
Closing the issue due to inactivity. |
Terraform CLI Version
0.14.11
Terraform Provider Version
0.94.1
Terraform Configuration
Category
category:resource
Object type(s)
resource:procedure
Expected Behavior
It should have created successfully, and plan should have been applied without any error.
Actual Behavior
Failed with error as following
Steps to Reproduce
Use terraform configuration and just hit terraform apply after making plan
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: