quick-wolf-8403
05/08/2022, 4:27 PMpulumi config cp
to move secrets and config entries from the old stack.alert-balloon-36955
05/09/2022, 1:14 AMfuture-window-78560
05/09/2022, 4:55 AMmicroscopic-cpu-38113
05/09/2022, 5:00 AMadorable-gpu-98268
05/09/2022, 10:34 AMadorable-gpu-98268
05/09/2022, 11:37 AMdualStackIPv6
I can set this using the aws cli, but I’ve a multi-account setup configured with pulumi and would need to set that for every account.delightful-monkey-90700
05/09/2022, 1:56 PMfuture-window-78560
05/09/2022, 3:15 PMnutritious-battery-42762
05/09/2022, 4:29 PMfuture-refrigerator-88869
05/09/2022, 4:43 PMaws-auth
configmap (or any configmap for that matter) after the cluster has been created ?
In my case, I have the eks cluster created with some roleMappings
but some workloads that get deployed might want to create a specific least-privileged user. I'd need to edit the existing ConfigMap
for aws-auth
after cluster creation but I can't figure a way to do it. Any help is appreciated 🙌straight-crayon-4578
05/09/2022, 7:50 PM__main__.py
file,
even though the imported code isn't at main file, the CLI keeps prompting Preview failed: unable to delete resource...
future-window-78560
05/10/2022, 3:25 AMadorable-gpu-98268
05/10/2022, 6:51 AMcool-glass-63014
05/10/2022, 7:15 AMcool-glass-63014
05/10/2022, 7:15 AMbulky-agent-73210
05/10/2022, 11:59 AMnutritious-jelly-29541
05/10/2022, 1:00 PMbland-lawyer-98859
05/10/2022, 1:47 PMsecret_version = aws.secretsmanager.SecretVersion(f"aws_secretversion_{secret_name}", secret_id=secret.id, secret_string=json.dumps(secret_value))
Pulumi preview output :
[urn=urn:pulumi:dev::snowflake::aws:secretsmanager/secretVersion:SecretVersion::aws_secretversion_snowflake/user/dev_usr_finops_api]
[provider=urn:pulumi:dev::snowflake::pulumi:providers:aws::default_4_38_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
secretId : output<string>
secretString: (json) {
password : "nDXw\">)ElJK=D+4$IvyJoBrbXR.LNF"
username : "TEST"
}
magnificent-lifeguard-15082
05/10/2022, 4:01 PMerror: It looks like the Pulumi SDK has not been installed. Have you run npm install or yarn install?
after updating the pulumi version and updating my checkout on another machine - upgrade was fine on ci and the machine i did the bump on but now ive switched and getting this. additional context: using nix to manage pulumi-bin installechoing-motherboard-16358
05/10/2022, 8:25 PMversion
parameter to my config and splitting my Pulumi code into src/v1
and src/v2
. This would involve a lot of duplication. Any thoughts on a more elegant solution?microscopic-cpu-38113
05/11/2022, 6:57 AMmicroscopic-cpu-38113
05/11/2022, 6:58 AMblue-actor-6315
05/11/2022, 9:24 AMbig-horse-80180
05/11/2022, 9:31 AMWebAclAssociation
resource requires ARNs which can't be manually set from both the APIGW and Web ACL. Not sure the best way to go about this (working in TypeScript) or if it's possible. I'd be wanting to test the policy with assertNoStackViolations
white-chef-55657
05/11/2022, 12:27 PMfancy-spoon-46046
05/11/2022, 1:05 PMwhite-chef-55657
05/11/2022, 2:22 PMagreeable-king-2755
05/11/2022, 2:36 PMpulumi up
for the first time. They've logged in the CLI, set a stack (an existing one I've deployed to before) and they also put our machine user IAM deployer keys in ~/.aws/credentials
.broad-raincoat-27115
05/11/2022, 2:48 PMdelightful-monkey-90700
05/11/2022, 3:31 PM