Hi all, upgraded from pulumi v2 to v3. I am seeing...
# typescriptp
proud-spoon-58287
05/13/2021, 11:42 AMHi all, upgraded from pulumi v2 to v3. I am seeing a strange error with this part:
Copy code
aws:elasticache:Cluster (data-feed-control):
error: unmarshaling urn:pulumi:development::platform-data-feed::aws:elasticache/cluster:Cluster::data-feed-control's instance state: could not read field snapshot_arns: '' expected type 'string', got unconvertible type '[]interface {}', value: '[]' Copy code
return new aws.elasticache.Cluster('data-feed-control', {
clusterId: 'data-feed-control',
engine: 'redis',
engineVersion: '6.x',
nodeType: 'cache.t3.micro',
numCacheNodes: 1,
parameterGroupName: 'default.redis6.x',
securityGroupIds: [defaultSecurityGroup.id],
subnetGroupName: feedControlSubnetGroup.id
})proud-spoon-58287
05/13/2021, 11:45 AMsnapshot_arns is not mandatory
proud-spoon-58287
05/13/2021, 11:45 AMdo not get what it wants
p
proud-spoon-58287
05/13/2021, 12:06 PM@cool-fireman-90027 point is that I do not need any snapshot.
proud-spoon-58287
05/13/2021, 12:07 PMcan I not simply not passing anything since it is an optional parameter?
proud-spoon-58287
05/13/2021, 12:08 PMthis is the code
proud-spoon-58287
05/13/2021, 12:08 PM Copy code
return new aws.elasticache.Cluster('data-feed-control', {
clusterId: 'data-feed-control',
engine: 'redis',
engineVersion: '6.x',
nodeType: 'cache.t3.micro',
numCacheNodes: 1,
parameterGroupName: 'default.redis6.x',
securityGroupIds: [defaultSecurityGroup.id],
subnetGroupName: feedControlSubnetGroup.id
})proud-spoon-58287
05/13/2021, 12:08 PMeven if I copy the one in the docs, fails with the same error
c
cool-fireman-90027
05/13/2021, 12:22 PMThere is a work around here
p
proud-spoon-58287
05/13/2021, 1:04 PMthanks mate
proud-spoon-58287
05/13/2021, 2:33 PMI have manually removed the existing redis instance from aws console
proud-spoon-58287
05/13/2021, 2:34 PMran pulumy refresh
proud-spoon-58287
05/13/2021, 2:34 PMBUT
proud-spoon-58287
05/13/2021, 2:34 PMno changes were detected
proud-spoon-58287
05/13/2021, 2:34 PMand now I cannot do pulumi up anymore since it is trying to update something that does not exists anymore
proud-spoon-58287
05/13/2021, 2:35 PMI tried to export the stack and remove it manually, but it is in 16 different entries and I don't think that is the right way to do it
proud-spoon-58287
05/13/2021, 2:35 PMwhat is the right approach for this case?
a
aloof-address-12777
05/13/2021, 2:57 PMHave you tried
pulumi up -rc
cool-fireman-90027
05/13/2021, 3:44 PMYou can use pulumi state delete to remove it from the state file that you exported. Then if you import the state file, and do a
pulumi upp
proud-spoon-58287
05/13/2021, 5:56 PMneed to try it
proud-spoon-58287
05/13/2021, 5:59 PMthanks @cool-fireman-90027
proud-spoon-58287
05/14/2021, 2:39 PM@cool-fireman-90027
proud-spoon-58287
05/14/2021, 2:39 PMlast bug/help
proud-spoon-58287
05/14/2021, 2:39 PM Copy code
aws:iam:RolePolicyAttachment (iamrpa-data-feed-lambda-role-lambda-access-policy):
error: 1 error occurred:
* Error attaching policy arn:aws:iam::aws:policy/AWSLambdaFullAccess to IAM Role iamr-data-feed-lambda-71c3895: NoSuchEntity: Policy arn:aws:iam::aws:policy/AWSLambdaFullAccess does not exist or is not attachable.
status code: 404, request id: a306fb38-152c-40a4-a922-d44802d8e8d4proud-spoon-58287
05/14/2021, 2:39 PMI know that AWSLambdaFullAccess is now deprecated and no longer attachable
proud-spoon-58287
05/14/2021, 2:40 PMis this a known bug?
proud-spoon-58287
05/14/2021, 2:46 PMforget it 🙂
proud-spoon-58287
05/14/2021, 2:46 PMmy fault