Open jkodroff opened 1 year ago
Thanks for reporting this @jkodroff. The fix will be in the bridge, so I opened https://github.com/pulumi/pulumi-terraform-bridge/issues/1297 to track.
Hi there,
I also got this message. In this case, what is the recommended action from our end?
You will need to switch to a non-deprecated resource. The Pulumi token is "snowflake:index/grantPrivilegesToRole:GrantPrivilegesToRole"
. This corresponds to:
Is there any example?
That is a big change for the grant schema is there any documentation on it?
Sorry, one more question, does it make the grant stop working?
@rvasconcelossilva
Does it make the grant stop working?
Not entirely sure if this is what you're asking, but the StageGrant
resource still works, it's just that you get a deprecation warning. I was not able to figure out the syntax for granting to a Stage using GrantPrivilegesToRole
when I filed this issue and just continued using StageGrant
. The code I was working on will eventually be publicly available (maybe even this week). I'll post the example I was working on if you let me know you want to see it.
However, I think that the docs might've gotten updated since I originally filed the issue, because it looks like GrantPrivilegesToRole.onSchemaObject
is the right way to specify a grant to a STAGE
: https://www.pulumi.com/registry/packages/snowflake/api-docs/grantprivilegestorole/#grantprivilegestoroleonschemaobject
Good luck, and please post your code if you get something working! I'll do the same if I can get GrantPrivilegesToRole
working with a STAGE
.
Is there some where I can see the change? I believe there are changes in the arguments and many other things right? I believe any deprecated resource should have a how to migrate to the new one. Is there a way to help with that?
What happened?
Creating a resource of type
snowflake.StageGrant
gives the user a deprecation warning that references the TF name:Expected Behavior
n/a
Steps to reproduce
n/a
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).