best-xylophone-83824
08/27/2019, 9:56 AMgifted-engine-92308
08/27/2019, 12:48 PMdamp-room-71337
08/27/2019, 2:05 PMmodern-army-90330
08/27/2019, 7:05 PMbitter-dentist-28132
08/27/2019, 8:58 PMpulumi up
has finished, it unlocks the stack. this doesn't seem to be the case; the staging job gets a 409 error. is this a bug, or a known problem with app.pulumi.com's concurrency management?colossal-plastic-46140
08/27/2019, 9:02 PMloud-nest-15724
08/28/2019, 1:29 PMconst region: string = new pulumi.Config().require("aws:region");
bored-river-53178
08/28/2019, 2:27 PMpulumi stack rename
resulted in error: error: rename .pulumi/history/dev-bfstack-emesa1 .pulumi/history/dev-bfstack-emesa: no such file or directory
the state is was in s3
now I can access the stack at all, pulumi up
gives the error 'error: failed to load checkpoint: blob (code=NotFound): NoSuchKey: The specified key does not exist.
status code: 404, request id: 52CA127D3A77A221, host id: +t5rZUXVdawXQCrYFQrMX4KWh3Us/vWLu9ltJ7Hj01aHn2Irz8c2QCkztOqEyHlhVhHrBTvNT+0='bored-river-53178
08/28/2019, 2:28 PMbest-xylophone-83824
08/28/2019, 3:00 PMcool-egg-852
08/28/2019, 3:08 PMgcp.config.project
I thinkbest-xylophone-83824
08/28/2019, 3:13 PMdamp-room-71337
08/28/2019, 3:14 PMeks.Cluster
would get stuck on destroy when trying to delete a node security group?
aws:ec2:SecurityGroup cluster-nodeSecurityGroup deleting...
damp-room-71337
08/28/2019, 3:16 PMdamp-room-71337
08/28/2019, 3:17 PMmodern-ram-22318
08/28/2019, 3:59 PMpulumi up
all executes fine, but my LaunchConfiguration and AutoScalingGroup never actually get created in AWS, don't show up in my stack Resources. Everything else so far seems to be working fine. Any ideas on why that would be?
Also, any idea if it's possible to add Metadata to LaunchConfiguration resources?flat-guitar-86436
08/28/2019, 6:31 PMsome-doctor-62800
08/28/2019, 7:14 PMflat-guitar-86436
08/28/2019, 9:23 PMexport const rootAccount = new aws.organizations.Account(INFRA_CONFIG.REFERENCE_ACCOUNT_NAME, {
email: INFRA_CONFIG.ROOT_ACCOUNT_EMAIL,
iamUserAccessToBilling: 'ALLOW',
parentId: rootOrgUnit.id
});
is it possible to do that? Pulumi error because this user already existdamp-room-71337
08/29/2019, 9:46 AMvpcCniOptions
on eks.Cluster
doesn’t seem to be taking effect? With this definition:
new eks.Cluster(
"cluster",
{
name: opts.tagName,
version: opts.version,
vpcId: opts.vpcId,
vpcCniOptions: {
logLevel: "INFO",
warmEniTarget: 0
}
}
);
the aws-node
env vars look like:
Environment:
AWS_VPC_K8S_CNI_LOGLEVEL: DEBUG
AWS_VPC_K8S_CNI_LOG_FILE: stdout
MY_NODE_NAME: (v1:spec.nodeName)
damp-room-71337
08/29/2019, 9:47 AMUpdating (dev):
Type Name Status Info
pulumi:pulumi:Stack cluster-infrastructure-dev
└─ cluster-infrastructure:eksCluster cluster
└─ eks:index:Cluster cluster
~ └─ pulumi-nodejs:dynamic:Resource cluster-vpc-cni updated [diff: +logLevel]
I’ve tried deleting instances in the nodegroup and letting the ASG replace them, but the env vars are still the sameflat-lamp-55912
08/29/2019, 12:20 PMincalculable-diamond-5088
08/29/2019, 2:03 PMXXX refers to unknown provider YYY
error with the state remaining inconsistent. That’s a problemsome-doctor-62800
08/29/2019, 3:35 PMsome-doctor-62800
08/29/2019, 3:43 PMsome-doctor-62800
08/29/2019, 3:44 PMgcp.projects.getProject
but on gcp.organizations.getProject
bitter-judge-29436
08/29/2019, 4:35 PMbitter-judge-29436
08/29/2019, 4:35 PMhigh-translator-22614
08/29/2019, 4:48 PMhigh-translator-22614
08/29/2019, 4:48 PMhigh-translator-22614
08/29/2019, 4:48 PM