adamant-dress-73325
09/09/2019, 7:48 PMtall-oyster-54217
09/09/2019, 7:51 PMcareful-baker-18386
09/09/2019, 8:01 PMpulumi up
i get the following in my debug output:
Diagnostics:
aws:s3:Bucket (my-bucket):
error: error validating provider credentials: error calling sts:GetCallerIdentity: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
pulumi:pulumi:Stack (pulu-dev):
debug: Registering resource: t=pulumi:pulumi:Stack, name=pulu-dev, custom=false
debug: RegisterResource RPC prepared: t=pulumi:pulumi:Stack, name=pulu-dev
debug: RegisterResource RPC finished: resource:pulu-dev[pulumi:pulumi:Stack]; err: null, resp: urn:pulumi:dev::pulu::pulumi:pulumi:Stack::pulu-dev,,,,
debug: Running program '/Users/leif/Sites/pulu' in pwd '/Users/leif/Sites/pulu' w/ args:
debug: Registering resource: t=aws:s3/bucket:Bucket, name=my-bucket, custom=true
debug: RegisterResource RPC prepared: t=aws:s3/bucket:Bucket, name=my-bucket
debug: Setting AWS metadata API timeout to 100ms
debug: Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
debug: No assume_role block read from configuration
debug: Building AWS auth structure
debug: Setting AWS metadata API timeout to 100ms
debug: Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
debug: AWS Auth using Profile: "carpedalan"
debug: Trying to get account information via sts:GetCallerIdentity
little-garage-43399
09/09/2019, 9:13 PMicy-engineer-10830
09/09/2019, 9:27 PMworried-city-86458
09/09/2019, 9:56 PMindex.ts
and fail earlyworried-city-86458
09/09/2019, 10:29 PMbusy-umbrella-36067
09/10/2019, 12:22 AMkubeernetes.helm.v2.Chart
and exporting all of them would be tedious.tall-oyster-54217
09/10/2019, 8:58 AMdamp-room-71337
09/10/2019, 9:04 AMconfig set
? This: pulumi config set aws:profile synchronicity
returns error: failed to load checkpoint: blob (code=Unknown): NoCredentialProviders: no valid providers in chain. Deprecated.
on pulumi up
, while setting AWS_PROFILE=
works finebetter-actor-92669
09/10/2019, 11:34 AMdamp-room-71337
09/10/2019, 3:11 PMpulumi stack ls
not be showing all stacks, when using S3 backend?damp-room-71337
09/10/2019, 3:11 PMpulumi stack init newstack
works, and I can see the stack state json in S3 next to the stacks that arenāt being returneddamp-room-71337
09/10/2019, 3:17 PM$ pulumi stack ls -a
NAME LAST UPDATE RESOURCE COUNT
dev-red* n/a n/a
$ pulumi stack init dev
error: stack 'dev' already exists
$ pulumi stack ls -a
NAME LAST UPDATE RESOURCE COUNT
dev-red* n/a n/a
$ pulumi stack ls -a
NAME LAST UPDATE RESOURCE COUNT
dev 23 hours ago 21
dev-red* n/a n/a
damp-room-71337
09/10/2019, 3:17 PMicy-engineer-10830
09/10/2019, 4:08 PMbright-architect-36509
09/10/2019, 5:19 PMpulumi login --local
I'm not able to login to the pulumi backend anymore. I tried pulumi login
, pulumi login <http://app.pulumi.com|app.pulumi.com>
. I'm getting this error
error: problem logging in: getting user info from <http://app.pulumi.com>: unmarshalling response object: invalid character '<' looking for beginning of value
quiet-wolf-18467
rrdatas: [computeInstance.networkInterfaces[0].accessConfigs[0]?.natIp]
I can't seem to get this to work. accessConfigs is an optional, so could be emptywide-holiday-59376
09/10/2019, 7:07 PMavailabilityZone
? Is there a way to use the default zone like we get when creating new ec2 instances?wide-holiday-59376
09/10/2019, 7:10 PMquiet-wolf-18467
wide-holiday-59376
09/10/2019, 7:18 PMwide-holiday-59376
09/10/2019, 7:18 PMquiet-wolf-18467
wide-holiday-59376
09/10/2019, 7:39 PM"Invalid value '/dev/xvda' for unixDevice. Attachment point /dev/xvda is already in use", code: "InvalidParameterValue"
wide-holiday-59376
09/10/2019, 7:39 PMwide-holiday-59376
09/10/2019, 7:45 PMwide-holiday-59376
09/10/2019, 7:45 PMquiet-wolf-18467
wide-holiday-59376
09/10/2019, 7:50 PM