I'm upgrading `pulumi-snowflake` from 0.55.0 to 2.5.0 (big jump, I know!), and I'm encountering this...
d
I'm upgrading
pulumi-snowflake
from 0.55.0 to 2.5.0 (big jump, I know!), and I'm encountering this strange error when updating my Tasks:
[schedule[0]] missing expected {
. If I change the
resource_name
to force a deletion and creation of a new identical Task, I don't get this error. All of my Tasks have been updated to the new API with
TaskScheduleArgs
. I'm trying to avoid the recreation because all of my Tasks -- and there are a lot of them -- are protected from accidental deletion, so it would require a painfully manual process to migrate.
1
s
If you could recreate them easily (IOW, if we could automate removing the delete production), would that solve most of the problem for you? Asking b/c IDK if Snowflake tasks are stateful or not.
d
Yes I think that would be sufficient. They are stateless
s
The
pulumi state unprotect
command might be what you want: https://www.pulumi.com/docs/iac/cli/commands/pulumi_state_unprotect/
w
@dazzling-art-25825 just following up here, did this resolve your issue?
d
It didn't. Still getting used to this repo in my new job. Things are "protected" with
retain_on_delete=True
but
protect=False
. I can change that now (took me a bit to confirm it had actually changed with state export since options don't seem to show up in preview), but I'm still working through this issue which has unfortunately grown into many simultaneous problems. Currently debating just importing into a fresh stack on the newest version to avoid this mess.
w
So protect is false and retain on delete is false but it still is failing?
d
No that works but I abandoned this particular effort because there were too many other issues. My strategy has been to import everything into a fresh stack. But guess what... that isn't going so seamlessly either, unfortunately. Opening up a new thread for my issues. Thanks for responding!
😅 1
👍 1
w
Sounds good!