flat-insurance-25294
03/13/2021, 2:29 PMbroad-dog-22463
03/13/2021, 2:32 PMflat-insurance-25294
03/13/2021, 2:33 PMwooden-room-54680
03/15/2021, 5:49 PMmillions-furniture-75402
03/15/2021, 7:09 PMaws.s3.Bucket.get()
and receiving a strange error that seems to indicate it’s somehow related to stack references (which I’m not using in this project: registered twice (read and read)
I’ve tried getting my Bucket 3 different ways:
aws.s3.Bucket.get(bucketName, bucketName, { name: bucketName });
aws.s3.Bucket.get(bucketName, bucketName);
aws.s3.Bucket.get(bucketName);
Furthermore, it breaks the update, and tells me to import an exported stack.
Now I have some buckets with 2-3 extra -[a-z0-9]{7}
suffixeslemon-machine-35564
03/15/2021, 7:42 PMUnsupported 'maximumBatchingWindowInSeconds' parameter for given event source
powerful-art-3002
03/16/2021, 9:03 AMpolite-student-92901
03/16/2021, 4:57 PMrhythmic-nail-73192
03/16/2021, 5:57 PMquaint-electrician-41503
03/16/2021, 7:57 PMResources:
- 22 to delete
Do you want to perform this destroy? yes
Destroying (dev):
Type Name Status Info
pulumi:pulumi:Stack pulumi-vpc-ts-dev **failed** 1 error
- └─ aws:ec2:InternetGateway clientVpc1 **deleting failed** 1 error
Diagnostics:
aws:ec2:InternetGateway (clientVpc1):
error: deleting urn:pulumi:dev::pulumi-vpc-ts::awsx:x:ec2:Vpc$awsx:x:ec2:InternetGateway$aws:ec2/internetGateway:InternetGateway::clientVpc1: 1 error occurred:
* Error waiting for internet gateway (igw-07bf9c311ca705fe8) to detach: couldn't find resource (31 retries)
pulumi:pulumi:Stack (pulumi-vpc-ts-dev):
error: update failed
damp-school-17708
03/17/2021, 10:47 AMupdate [diff: ~viewerCertificate]
even if I didn't make any change to my cloudfront configuration, is there any way to avoid this?
there's nothing fancy over there, it's just a cloudfront domain without route53, pointing to an s3 bucket
viewerCertificate: {
cloudfrontDefaultCertificate: true,
sslSupportMethod: 'sni-only',
},
creamy-minister-70065
03/17/2021, 12:53 PMchilly-magazine-6129
03/17/2021, 10:49 PMnutritious-shampoo-16116
03/18/2021, 10:41 AMcurved-pharmacist-41509
03/18/2021, 12:34 PMmillions-furniture-75402
03/18/2021, 2:28 PMexport const { accountId } = pulumi.output(aws.getCallerIdentity());
big-potato-91793
03/18/2021, 8:04 PMpolite-student-92901
03/18/2021, 9:53 PMwhite-secretary-18260
03/19/2021, 8:23 PMbroad-gold-44713
03/22/2021, 4:38 AMerror: Preview failed: 1 error occurred:
* error configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found.
I followed a recent thread and set a bunch of config variables, but that doesn't help
aws:profile xxxxxx
aws:region us-east-1
aws:skipCredentialsValidation false
aws:skipGetEc2Platforms false
aws:skipMetadataApiCheck false
aws:skipRegionValidation false
I'm using Pulumi 2.23.1. Tried going back a few versions, but that didn't help either.
I know the credentials from the aws:profile work because I can use them with awscli.bitter-toddler-22112
03/22/2021, 12:09 PMwhite-secretary-18260
03/22/2021, 1:54 PMiamRoles
property I get an error saying:
DBClusterRoleNotFound: Role ARN arn:aws:iam::xxx:role/xxx-xxx cannot be found for DB Cluster: xxx. Verify your role ARN and try again. You might need to include the feature-name parameter.
if I use RoleAssociation
which has feature name I get an error like:
error associating RDS DB Instance (api-rds-cluster-dev) IAM Role (arn:aws:iam::xxx:role/xxx): DBInstanceNotFound: DBInstance not found: xxx
What’s a good working example of creating an RDS cluster with a role associated to it?salmon-ghost-86211
03/22/2021, 9:58 PMaws.iam.Group.get
method to get the group, but I'm not sure how to actually access the existing group membership.alert-raincoat-81485
03/23/2021, 2:04 AMinstance_refresh=aws.autoscaling.GroupInstanceRefreshArgs(
strategy="Rolling",
preferences=aws.autoscaling.GroupInstanceRefreshPreferencesArgs(
instance_warmup=120,
min_healthy_percentage=50,
),
triggers=["launch_template"],
),
Can someone please help and guide?quick-garden-9190
03/23/2021, 6:30 PMdesiredSize
is a required value. This size will clobber whatever the cluster-autoscaler has landed on.
I’ve tried using ignoreChanges: ['scalingConfig.desiredSize']
but this option seems to be completely ignored.
I’ve tried searching through the docs, it seems like this example is missing some key functionality, unless I’m not seeing something obvious.damp-school-17708
03/24/2021, 9:56 AM```Previewing update (tam):
Type Name Plan Info
+ pulumi:pulumi:Stack link-tam create
└─ pulumi:providers:aws default_3_31_0 1 error
Diagnostics:
pulumi:providers:aws (default_3_31_0):
error: no resource plugin 'aws-v3.31.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource aws v3.31.0`
```damp-school-17708
03/24/2021, 9:57 AMmicroscopic-dress-1605
03/24/2021, 9:25 PMquaint-guitar-13446
03/25/2021, 12:24 AMOnly one of host_header, http_header, http_request_method, path_pattern, query_string or source_ip can be set in a condition block
quaint-guitar-13446
03/25/2021, 12:24 AM