many-salesmen-89069
09/28/2021, 6:53 PMpurple-train-14007
09/28/2021, 9:47 PMrapid-raincoat-36492
09/28/2021, 10:24 PMPulumi.<stack-name>.yaml
files created for every branch in git?busy-house-95123
09/28/2021, 11:00 PMsteep-toddler-94095
09/29/2021, 1:06 AMspec.controller
field of an IngressClass
is immutable so the resource needs to be recreated. Not sure by which mechanism Pulumi does that, but should I create a ticket for this?many-salesmen-89069
09/29/2021, 7:46 AM--config-file
flag is not supported.white-cat-90296
09/29/2021, 8:53 AMRemoteArchive
on an S3
bucket? I'm trying to use it as the source code for a Lambda
function. The docs say that the URI should be http/https/file and it doesn't accept s3:// - https://www.pulumi.com/docs/intro/concepts/assets-archives/ - Any ideas for a viable workaround? Opening up the bucket to http access wouldn't work in this case.alert-london-63088
09/29/2021, 10:46 AMlittle-summer-88406
09/29/2021, 1:50 PMtall-ocean-85516
09/29/2021, 4:02 PMrapid-raincoat-36492
09/29/2021, 6:04 PMconst helloWorldFn = new lambda.Function('hello-world', {
code: new asset.FileArchive(`${__dirname}/../../build`),
handler: 'build/src/index.telemetryClassifierHandler',
name: 'pulumiTestFn',
publish: true,
role: role.arn,
runtime: 'nodejs14.x',
tracingConfig: {
mode: 'ACTIVE',
},
});
I am seeing a ValidationError
like in the attached image, however I can upload a zip file of that directory in the AWS console (or via serverless and/or terraform) and all of them seem to be okay with the contents of the build
dir. I have tried creating a zip file separately and using that file as the FileArchive
, as well as changing the handler to include the build/
prefix or not
I don't see any useful logs on what is failing to validate when using --debug
or --verbose 4
.
Has anyone seen this before, or know how to debug what is wrong?full-artist-27215
09/29/2021, 6:24 PMbulky-area-51023
09/29/2021, 7:14 PMflat-appointment-12338
09/29/2021, 7:50 PMawsx.ecs.Image.fromDockerBuild
to create my docker image that gets deployed but it seems that it will always attempt to build and deploy a new docker image even if the image is unchanged. I often find myself changing other parts of the infrastructure but would prefer not to have to do an entire build. Is there any way to avoid this?rhythmic-rain-31941
09/29/2021, 7:56 PMhundreds-traffic-617
09/29/2021, 9:12 PMpulumi config set --secret
seems to be purely a local modification until I were to deploy from my machine I guess. But I obviously don't want to deploy to production from my laptop just to update the config.busy-house-95123
09/29/2021, 10:52 PMrhythmic-rain-31941
09/29/2021, 11:37 PMrancher_ci_cluster = rancher2.Cluster()
chart = rancher2.AppV2("cluster-autoscaler",
cluster_id=rancher_ci_cluster.id,
namespace="kube-system",
repo_name=catalog.name.apply(lambda name: name),
chart_name="cluster-autoscaler",
chart_version="9.10.7",
values=f"""
awsRegion: {config.require("rancherAwsCiRegion")}
autoDiscovery:
clusterName: {rancher_ci_cluster.name.apply(lambda name: name)}
extraArgs:
balance-similar-node-groups: true
priorityClassName: system-cluster-critical
""",
opts=ResourceOptions(depends_on=catalog)
)
so in the above snippet i could read the rancher_ci_cluster.id without any apply() or all() . but for looking up name even though i used rancher_ci_cluster.name.apply(lambda name: name)
i still see it as an object instead of raw data <pulumi.output.Output object at 0x103a73e20>
. so can anyone help me understand what is that im missing here and how the behavior works?better-baker-47643
09/29/2021, 11:59 PMconst lb = new awsx.lb.ApplicationLoadBalancer(`hasura-${env}`);
const listener = lb.createListener(`hasura-listener-${env}`, {
protocol: "HTTPS",
certificateArn: sslCertificateValidation.certificateArn,
});
const hasuraService = new awsx.ecs.FargateService(
`hasura-${env}`,
{
cluster,
desiredCount: 1,
taskDefinitionArgs: {
logGroup: logGroup,
cpu: "1024",
memory: "2048",
containers: {
service: {
// logConfiguration: {
// logDriver: "awslogs",
// options: {
// "awslogs-group": logGroup.id,
// "awslogs-region": awsRegion!,
// "awslogs-stream-prefix": `hasura-${env}`,
// },
// },
image: hasuraImage,
portMappings: [listener], ....
many-salesmen-89069
09/30/2021, 7:14 AMquiet-architect-91246
09/30/2021, 9:34 AMpulumi up
I use the -C parameter like this: pulumi up -y -C pulumi
, since I use a subdirectory in our project for everything pulumi related. Sadly this doesnt pick up tsconfig.json, which is defined at root level of the project (the directory in which I run the mentioned command). Is there anyway to tell pulumi where to look for tsconfig.json? It works to just copy tsconfig into the /pulumi directory, but id greatly prefer to not have it twice in our project.hundreds-airport-37168
09/30/2021, 2:33 PMrhythmic-rain-31941
09/30/2021, 6:48 PMexec
as we can do in terraform provider? https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#exec-plugins
#generalrapid-raincoat-36492
09/30/2021, 8:09 PMalert-glass-49407
09/30/2021, 8:32 PMname
on Trail
resource properties looks like it erroneously has the description for TrailAdvancedEventSelector
's name
gorgeous-minister-41131
09/30/2021, 9:32 PMmissing_text_or_fallback_or_attachments
miniature-nest-23801
10/01/2021, 12:51 AMbrash-kite-78002
10/01/2021, 12:46 PMdry-autumn-28966
10/01/2021, 1:13 PMpolite-article-56500
10/01/2021, 6:45 PM500
when tried to import, someone know any solution?