Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
m
melodic-car-16900
02/25/2022, 4:46 PMhas anyone come across this error recently?
pulumi:pulumi:Stack (mast-snowflake-non-pro):
error: preview failed
snowflake:index:RoleGrants (snowflake_user_reader_role_grant):
error: Preview failed: refreshing urn:pulumi:non-pro::mast-snowflake::snowflake:index/roleGrants:RoleGrants::snowflake_user_reader_role_grant: 1 error occurred:
* 5 or 6 fields allowede
echoing-dinner-19531
02/25/2022, 4:51 PMCan you use
pulumi stack exportidm
melodic-car-16900
02/25/2022, 4:52 PMe
echoing-dinner-19531
02/25/2022, 4:55 PMAre you running
preview--refreshpreview/up
m
melodic-car-16900
02/25/2022, 4:57 PMit's caused by refreshing
I noticed it was causing failures in ci whilst running
pulumi up --refreshand then locally I've been able to reproduce the error just by calling
pulumi refreshpulumi upbut doesn't fix the issue
e
echoing-dinner-19531
02/25/2022, 4:58 PMThe format of IDs changed: https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/824
I think if you do an update without refresh it should just write out the new format IDs
m
melodic-car-16900
02/25/2022, 4:58 PMgood find, thank you
unfortunately this hasn't solved the issue
wait, perhaps it has, 1 moment
Hey, just to round this off, I ended up having to remove the resources and then recreate them to make it work
Thanks for your help
e
echoing-dinner-19531
02/26/2022, 3:55 PMAh that's annoying sorry things didn't just work, our engine doesn't expect resource IDs to change like this bit of an awkward breaking change from the Snowflake provider.