I m trying to get our Redis deployment files updated and whe

Question

I m trying to get our Redis deployment files updated and when I run pulumi up I am getting this error back I have tried to export my state for the stack and remove the ` snapshotArns ` and reimport the state I am not sure what is causing this to break as it has worked before ``` aws elasticache Cluster redis temp error unmarshaling urn pulumi temp aws us east 1 redis aws elasticache cluster Cluster redis temp s instance state could not read field snapshot arns expected type string got unconvertible type interface value ```

purple-orange-91853 · Answer

This is the relevant section in the ts file for this deployment ``` const redis = new elasticache Cluster `redis $ deploymentName ` azMode numCacheNodes 1 engine redis engineVersion 6 x engineVersion 6 0 5 nodeType cache m4 large subnetGroupName redisSubnetGroup id securityGroupIds redisSecurityGroup id port 6379 ignoreChanges engineVersion ```

little-cartoon-10569 · Answer

You could try ignoring snapshotArns The docs say that snapshotArns must be a single element array so if ignoring it doesn t work you could try changing it to ` snapshotArns `

little-cartoon-10569 · Answer

However ignoring it looks like the safer option

purple-orange-91853 · Answer

let me try that

purple-orange-91853 · Answer

ok tried ` ignoreChanges snapshotArns ` and then tried `snapshotArns ` and `snapshotArns ` All three are producing errors The ignore changes produces this error ``` error aws elasticache cluster Cluster resource redis temp has a problem Attribute must be a single valu e not a list Examine values at Cluster SnapshotArns ``` While the last produced the same error as originally posted Using the ` ` in the middle gives me an error in the editor ```Type string is not assignable to type Input lt string gt | undefined Type string is not assignable to type string ```

little-cartoon-10569 · Answer

Hmm yea I read the definition of the param without reading the type of the param `string` is correct and the definition Single element string list is wrong

little-cartoon-10569 · Answer

Since the attribute is not in your code and the problem is happening during an `up` then I infer that there s a difference between what s in the state and what the provider requires Possibly the provider s version has changed recently Maybe running `pulumi refresh` at least on that resource would fix the Pulumi state

purple-orange-91853 · Answer

I have tried that I exported the state and manually deleted the two snapshotArns lines then imported that and did a refresh

little-cartoon-10569 · Answer

And refresh puts the snapshotArns back Hmm that s awkward

purple-orange-91853 · Answer

yeah

purple-orange-91853 · Answer

I ve put a refresh just before the pulumi up in my code deploy to see if that changes anything which is running now

little-cartoon-10569 · Answer

You can put ` refresh` in the parameters to a preview or up

purple-orange-91853 · Answer

good to know

little-cartoon-10569 · Answer

Also you can export just before and after a refresh to see what changes

little-cartoon-10569 · Answer

I think we should find out who created the provider and ask for help from dev team

little-cartoon-10569 · Answer

Or raise an issue on github

purple-orange-91853 · Answer

actually I think we already had that we have a ` r` in our pulumi up command

little-cartoon-10569 · Answer

Maybe try removing that after editing your state Perhaps you re fixing it then overwriting your fix before `up`ing

purple-orange-91853 · Answer

just tried the export remove the snapshotArns from the state file and then reimported did a `pulumi up non interactive yes r` which failed with the same error then re exported teh state to confirm and the snapshotArns lines were gone

little-cartoon-10569 · Answer

Try it without the ` r` That will be updating your state after you import it and before the `up`

little-cartoon-10569 · Answer

You want to test your version of the state not the providers version

little-cartoon-10569 · Answer

If that works then you know there s an issue bug in the provider and you should raise it in GitHub

purple-orange-91853 · Answer

ok so I removed the ` r` Manually refreshed the state with `pulumi refresh` exported the state and manually removed the lines containing `snapshotArns`and then re imported the state Then did `pulumi up non interactive yes` which has now resulted in a new error about existing securityGroups which is not related to the original issue

purple-orange-91853 · Answer

so it appears that by removing those lines from state and updating the state manually worked around the initial issue

purple-orange-91853 · Answer

without doing a `refresh` inbetween steps

purple-orange-91853 · Answer

I ll write up a bug report into Github tomorrow morning on this