curved-knife-45363
11/12/2021, 6:53 PMbland-winter-30535
11/13/2021, 12:41 AMgreat-greece-44955
11/15/2021, 5:44 AMpulumi up
) after correcting an issue with the configuration of an autoscaling group:
error: 1 error occurred:
* updating urn😛ulumi:dev::codicy-main::awsx:x:ecs:Cluster$awsx❌autoscaling:AutoScalingGroup$aws:cloudformation/stack:Stack::JupyterHub-AutoScalingGroup: 1 error occurred:
* error updating CloudFormation stack (arn:aws:cloudformation:ap-southeast-1:415375321442:stack/jupyterhub-autoscalinggroup-586cf84/2e25ca40-45d2-11ec-af4b-0af0cb546522): ValidationError: Stack:arn:aws:cloudformation:ap-southeast-1:415375321442:stack/jupyterhub-autoscalinggroup-586cf84/2e25ca40-45d2-11ec-af4b-0af0cb546522 is in ROLLBACK_COMPLETE state and can not be updated.
status code: 400, request id: 6c7e567b-4d0c-4903-afa1-876ea218fa1b
Does anyone have any suggestions?great-greece-44955
11/15/2021, 5:46 AMgreat-monkey-48685
11/15/2021, 12:36 PMdocker run -p 80:3000 container-id
How do I add the container port 3000 it to the fargate task definition, currently I’m doing:
const listener = new awsx.lb.ApplicationListener("pulumi-ecs-primary", {
external: true,
port: 80
});
const taskDefinition = new awsx.ecs.FargateTaskDefinition("sample", {
containers: {
sampleapp: {
image: awsx.ecs.Image.fromDockerBuild(sample, {
context: "./app/",
dockerfile: "./app/Dockerfile",
}),
portMappings: [listener]
},
},
});
thousands-area-40147
11/15/2021, 12:59 PMNewDBClusterIdentifier
parameter of the JS SDK v3 ModifyDBClusterCommand? It seems that simply changing the physical name of the resource in my pulumi script (i.e., changing the clusterIdentifier
parameter of the aws.rds.Cluster
resource) leads to a complete replacement, not a simple renaming. Any ideas?fancy-eve-82724
11/15/2021, 1:49 PMBlock public access
setting.little-cartoon-10569
11/16/2021, 2:39 AMwitty-belgium-75866
11/16/2021, 9:15 AMmillions-furniture-75402
11/16/2021, 8:08 PMbrave-nightfall-19158
11/17/2021, 4:55 PMwooden-student-58350
11/18/2021, 12:41 PMpulumi-nodejs
image I’m using doesn’t contain the docker binary).
What’s the best practice for dealing with this setup? I’d like to use the pulumi-nodejs
image if possible, so should I manually install docker in the CI script? Or is it better to use the docker
image and install Pulumi?brave-nightfall-19158
11/18/2021, 1:37 PMpowerful-furniture-83753
11/18/2021, 2:13 PMpulumi up
In this particular case, it's around nil pointers in lambda, but i also just had several fails with pushing to ECS which also seemed similar.numerous-printer-41511
11/19/2021, 1:18 AMpulumi up
against a specific AWS account (for a specific env)?numerous-printer-41511
11/19/2021, 1:19 AMaws sts assume-role
and then exporting the key/secret/token before each pulumi up/apply
?full-sugar-56177
11/19/2021, 9:20 AMbulky-painting-12886
11/19/2021, 9:59 AMpython-aws
. With one node group, which the minimum of two instances. However , I noted the two instances are hooked at the same sub-net. how do i make sure the instances will be in different sub-nets?bulky-painting-12886
11/19/2021, 9:59 AMfrom pulumi import ResourceOptions
from pulumi_aws import eks
cluster = eks.Cluster("cluster-dev",
role_arn=cluster_role.arn,
vpc_config=cluster_vpc_config,
version="1.20",
tags={"Name": "cluster-dev"},
opts=ResourceOptions(depends_on=cluster_subnets))
eks.NodeGroup("my-node",
capacity_type="SPOT",
cluster_name=cluster.name,
node_role_arn=node_role.arn,
subnet_ids=[public_subnet_a.id,
public_subnet_b.id],
scaling_config=eks.NodeGroupScalingConfigArgs(
desired_size=2,
max_size=4,
min_size=2),
tags={"Name": "my-node"},
opts=ResourceOptions(parent=cluster))
future-window-78560
11/19/2021, 2:13 PMagreeable-ram-97887
11/19/2021, 3:29 PMnumerous-printer-41511
11/19/2021, 5:02 PM.aws/credentials
?numerous-printer-41511
11/19/2021, 5:02 PMwitty-belgium-75866
11/19/2021, 7:58 PMbrave-nightfall-19158
11/22/2021, 9:27 AMpurple-lawyer-88338
11/22/2021, 1:17 PMmelodic-lifeguard-90736
11/22/2021, 4:20 PMnice-father-44210
11/23/2021, 5:35 PMpulumi_aws.get_caller_identity().account_id
seems to return the ci-cd account.high-holiday-63390
11/24/2021, 10:39 AMaws.ec2.getInstance
should take an instanceId
argumenthigh-holiday-63390
11/24/2021, 10:40 AM* One of filters, instance_tags, or instance_id must be assigned
high-holiday-63390
11/24/2021, 10:40 AM* One of filters, instance_tags, or instance_id must be assigned