purple-orange-91853
07/20/2021, 9:27 PM"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: '[]'
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
07/20/2021, 9:54 PM"snapshotArns":[""]
?purple-orange-91853
07/20/2021, 10:02 PM{ 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<string> | undefined'.
Type 'string[]' is not assignable to type 'string'.
little-cartoon-10569
07/20/2021, 10:28 PMstring
is correct, and the definition Single-element string list is wrong.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
07/20/2021, 10:37 PMlittle-cartoon-10569
07/20/2021, 10:37 PMpurple-orange-91853
07/20/2021, 10:37 PMlittle-cartoon-10569
07/20/2021, 10:38 PM--refresh
in the parameters to a preview or up...purple-orange-91853
07/20/2021, 10:39 PMlittle-cartoon-10569
07/20/2021, 10:39 PMpurple-orange-91853
07/20/2021, 10:40 PM-r
in our pulumi up commandlittle-cartoon-10569
07/20/2021, 10:42 PMpurple-orange-91853
07/20/2021, 10:44 PMpulumi up --non-interactive --yes -r
which failed with the same error. then re-exported teh state to confirm and the snapshotArns lines were gonelittle-cartoon-10569
07/20/2021, 10:45 PM-r
. That will be updating your state after you import it and before the up
.purple-orange-91853
07/20/2021, 10:54 PM-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.refresh
inbetween steps