wonderful-postman-42028
02/11/2022, 5:09 PMwonderful-postman-42028
02/11/2022, 5:09 PMmysterious-piano-88140
02/11/2022, 5:32 PMmammoth-art-6111
02/11/2022, 6:40 PMpurple-megabyte-83002
02/11/2022, 7:03 PM@aws-sdk
in a pulumi script but the code tries to run during the preview mode, how to make it behave like regular pulumi resources ?acceptable-oil-81004
02/11/2022, 7:08 PMastonishing-dinner-89046
02/11/2022, 9:31 PMsteep-beach-52652
02/12/2022, 4:01 PMripe-shampoo-80285
02/12/2022, 5:38 PMfancy-spoon-46046
02/12/2022, 9:13 PMstraight-cartoon-24485
02/12/2022, 10:59 PMgitlab-ci.yml
YAML in the DSL
To make my life easier, I've stumbled on: https://github.com/firecow/gitlab-ci-local - ideally I could compile a Pulumi program to generate the gitlab-ci.yml
and then run it locally for faster/debug-friendly dev cycles.
Any alternatives?able-hair-32695
02/12/2022, 11:29 PMlate-energy-66663
02/13/2022, 10:58 PMerror: could not create stack: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or manually delete the lock file(s).
Just wondering how I can manage and check if the stack is lock and manage it using automation api , instead of the deleting the stack file manually .best-lunch-95654
02/14/2022, 3:18 AM# example code
from pulumi import ResourceOptions
import pulumi_aws as aws
aws_vpc = aws.ec2.Vpc(
'my-vpc',
cidr_block = '10.0.0.0/16',
tags = default_tags
)
aws_public_subnet = aws.ec2.Subnet(
resource_name = 'public-subnet-change', # <= Originally a "public-subnet"
vpc_id = aws_vpc.id,
cidr_block = '10.0.1.0/24',
availability_zone = 'ap-northeast-2a',
tags = default_tags,
opts = ResourceOptions(delete_before_replace=True)
)
Do you want to perform this update? yes
Updating (dev):
Type Name Status Info
pulumipulumiStack pulumi-demo-dev failed 1 error
+ └─ awsec2Subnet public-subnet-change creating failed 1 error
Diagnostics:
pulumipulumiStack (pulumi-demo-dev):
error: update failed
awsec2Subnet (public-subnet-change):
error: 1 error occurred:
* error creating EC2 Subnet: InvalidSubnet.Conflict: The CIDR ‘10.0.1.0/24’ conflicts with another subnet
status code: 400, request id: *worried-xylophone-86184
02/14/2022, 3:52 AMbland-author-94126
02/14/2022, 8:15 AMwet-hydrogen-53006
02/14/2022, 10:49 AMlimited-rainbow-51650
02/14/2022, 11:19 AMpulumi-component-provider-go-boilerplate
repo. I built it and I executed the examples/simple stack. AWS resources are correctly created. Then I extended the code to register a resource transformation to tag the created AWS resources, based on this article. But it seems the transformation is not applied when I pass it to the StaticPage
component using the key transformations:
in opts
, nor when using pulumi.runtime.registerStackTransformation
. Are resource transformations in combination with component providers not supported?kind-room-82948
02/14/2022, 3:16 PMswift-monitor-84282
02/14/2022, 3:41 PMproud-art-41399
02/14/2022, 4:07 PMextra_options
supplied to DockerBuild
, e.g.
image = docker.Image(
"image-arm64",
build=docker.DockerBuild(
context="..",
extra_options=[
"--platform=linux/arm64",
"--output=type=docker",
"--cache-from=type=local,src=/tmp/.buildx-cache",
"--cache-to=type=local,mode=max,dest=/tmp/.buildx-cache",
],
),
image_name=repository.repository_url.apply(lambda url: f"{url}:arm64"),
registry=registry,
skip_push=False,
)
The first problem is that I can only build image for one architecture a time and can't use multiple values for --platform
(e.g. --platform=linux/amd64,linux/arm64
) because:
• I have to use the docker
output type as Pulumi uses docker inspect
after building the image (https://github.com/pulumi/pulumi-docker/blob/e2a25c62efc553515e784c0b241a2c946c888dd7/sdk/python/pulumi_docker/docker.py#L441).
• The docker
export type currently doesn't support multi-arch images (https://docs.docker.com/engine/reference/commandline/buildx_build/).
Even if I build images for distinct platforms separately, I'd need a way to create and push the manifest list (https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-multi-architecture-image.html). There's no such resource in the Docker provider, though.
For the motivation. I have a web app deployed as an ECS service running on AWS Fargate with autoscaling. I want to use a mix of Fargate and Fargate Spot, for tasks running on Fargate I'd like to use ARM64 architecture however Fargate Spot currently only supports x86-64 (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html).future-window-78560
02/14/2022, 9:52 PMgentle-piano-19726
02/14/2022, 10:22 PMmelodic-controller-83891
02/14/2022, 11:11 PMlittle-soccer-5693
02/15/2022, 1:21 AMtest-integ (aws:apigatewayv2:Integration)
error: aws:apigatewayv2/integration:Integration resource 'test-integ' has a problem: expected passthrough_behavior to be one of [WHEN_NO_MATCH NEVER WHEN_NO_TEMPLATES], got . Examine values at 'Integration.PassthroughBehavior'.
but initial deployment works fine. https://www.pulumi.com/registry/packages/aws/api-docs/apigatewayv2/integration/ describes PassthroughBehavior as only supported for WebSocket APIs but I'm creating an HTTP API. is this a bug?quaint-pillow-20530
02/15/2022, 9:36 AMquaint-pillow-20530
02/15/2022, 9:39 AMstocky-petabyte-29883
02/15/2022, 4:44 PMsteep-toddler-94095
02/15/2022, 5:18 PMpulumi login
command?steep-toddler-94095
02/15/2022, 5:56 PM