sticky-airline-40485
11/25/2021, 11:21 AMSystem.InvalidOperationException: This operation cannot be performed on a default instance of ImmutableArray<T>
errors. They pop up at random places and the only thing I can do is comment code, do pulumi up
, and then uncomment the code and hopefully it will go away. Anyone coming across thismagnificent-lifeguard-15082
11/25/2021, 3:56 PMlocal
and default
state backends? On the cloud a stack reference is derived from project name and stack name (ie. [ORG/]PROJECT/STACK
) but locally it’s just the stack (ie. STACK
). This means I end up with conflicts because every project has a "local"
stack. You can specify a location per login but I presume logging in separately for every project is going to be a pain and mean I cannot do anything in parallel (a non-starter).
Is my only solution to have an inconsistent stack name of “local-PROJECT” (Pulumi.production.yml
next to Pulumi.local-projec.yml
) or am I missing something else? Slightly unfortunate that I also have to propagate logic for handling name convention difference into my runtime for StackReference too.thankful-father-68341
11/26/2021, 4:28 AMthankful-father-68341
11/26/2021, 4:28 AMbrave-nightfall-19158
11/26/2021, 5:20 PMable-camera-57198
11/26/2021, 5:51 PMmost-lighter-95902
11/26/2021, 9:45 PMpulumi destroy
respect the dependsOn
option? I have two custom component resources where one dependsOn
the other, and it errors out because it destroys both in parallel. Anyway to make sure one is destroyed before the other?sparse-spring-91820
11/27/2021, 11:08 AMerror: [409] Conflict: Another update is currently in progress
errors?
I have pulumi job inside my circleci pipeline and if I merge multiple PRs in develop branch in a short time my build failsfierce-lion-84511
11/27/2021, 11:09 AMpulumi plugin install resource cloudinit v4.28.0:
the following error appears:
error: [resource plugin cloudinit-4.28.0] downloading from : 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-cloudinit-v4.28.0-windows-amd64.tar.gz>
• it looks like the access is denied, even if i try open that downlad url in my browser (see on image)
• And I cannot find anywhere, the lists of available plugins, or anything like that, does it even exists?
Investigation
• First of all what I see, the version which is it trying to download is wrong
◦ the current cloudInit version is 1.3.0 but it wants to download plugin for version 4.28.0
▪︎ The only 4.28.0 version library I have is @pulumi/aws, so there's some I think naming problem... because when I downgraded the @pulumi/aws to 4.27.0 it now wants to download cloudinit v4.27.0 which is wrong, this should always download 1.3.0 and the version shouldn't be based on aws library WTFFsteep-beach-52652
11/27/2021, 12:31 PMsteep-beach-52652
11/27/2021, 12:31 PMsteep-beach-52652
11/27/2021, 12:33 PMsteep-beach-52652
11/27/2021, 12:33 PMmagnificent-lifeguard-15082
11/27/2021, 12:58 PMprocess.cwd()
(nodejs) would be different between inline programs, automation and cli usage? Context: I'd like a ComponentResource (not contained within the project) to be able to look for config files in the project dir without having to pass a path explicitly through as an arg.wet-noon-14291
11/27/2021, 11:05 PMexport const myOutput = myConfig.get("secretProperty")
that the output isn't a secret? The behavior is strange since when you run the program it seems looks like it is a secret, but when you do pulumi stack output
it isn't. If I use getSecret
it works as intended. Why do we need both get
and getSecret
? I would be more than happy if pulumi just dealt with it so I don't have to think about if it is a secret or not when working with it .thankful-father-68341
11/28/2021, 6:24 AMrich-businessperson-35436
11/28/2021, 2:06 PMrich-businessperson-35436
11/28/2021, 10:46 PMfuture-refrigerator-88869
11/29/2021, 9:06 AMmagnificent-lifeguard-15082
11/29/2021, 3:18 PMPULUMI_NODEJS_CACHE_DYNAMIC_PROVIDERS=0
or PULUMI_NODEJS_CACHE_DYNAMIC_PROVIDERS=false
but it doesn't seem to be having any effect?little-soccer-5693
11/29/2021, 11:25 PMwitty-honey-13693
11/29/2021, 11:29 PMclean-gigabyte-10143
11/30/2021, 3:06 AMclient <- port 443 -> ALB <- port 80 -> Fargate task
square-coat-62279
11/30/2021, 10:55 AMsteep-beach-52652
11/30/2021, 1:45 PMsteep-beach-52652
11/30/2021, 1:46 PMsteep-window-60101
11/30/2021, 6:28 PMfrom pulumi_terraform import state
tf_state = state.RemoteStateReference("resources", "s3", state.S3BackendArgs(
bucket = "bucketName",
key = "terraform.tfstate",
region = "us-west-2"
))
pulumi.export('====', tf_state)
My terraform state file includes multiple terraform modules to build AWS ECS fargate cluster, which includes ALB, listener, security group, IAM, target group, fargate cluster, log group. But with RemoteStateReference, it only import the root outputs block, which is the output variables in outputs.tf in my terraform module. Is this by design or i missed anything? Thanks!square-coat-62279
11/30/2021, 6:37 PMalert-candle-88851
11/30/2021, 8:33 PM// docker-compose
agent:
image: ...
environment:
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro <-- ??? How do I convert these???
- /proc/:/host/proc/:ro
- /sys/fs/cgroup/:/host/sys/fs/cgroup:ro
I’m struggling to understand how the volumes syntax would map onto the Pulumi mount points interface. My pulumi code looks like this:
new awsx.ecs.FargateService('ecs-name', {
name: `resource-name`,
cluster: cluster,
taskDefinitionArgs: {
...
containers: {
containerName: {
...
mountPoints: [{???}]
}
}
},
...
})
Each MountPoint expects this type:
export interface MountPoint {
containerPath?: string;
readOnly?: boolean;
sourceVolume?: string;
}
When it comes to translating each of the volumes, how do I convert them to this format?
For example, what would the Pulumi MountPoint look like for this volume /var/run/docker.sock:/var/run/docker.sock:ro
? I’ve had limited success using the documentation. Thank you 🙏abundant-book-94104
11/30/2021, 10:48 PM