Any concern here?

have a question in the python channel. How do you extend a class to bake in values...I don't want to create a CRD though.

I can find this on the documentation: there's a way to set a tiemout for a helm chart to complete?

Looking at the api docs I see this markdown. I assume this should be a link to a Limits page? Anyone got that link?

ok found it in the repo that links to https://docs.aws.amazon.com/lambda/latest/dg/limits.html

Morning

Quick question, apologies if this has been covered else where. Is there any idea when C# might be bought into support?

Hi, how do ensure a resource is created after a Helm chart is deployed? If I use the variable the Helm chart is assigned to and add it to dependsOn for the following resource, the Helm chart still isn't deployed first.

So I have nginx

export const nginx = new k8s.helm.v2.Chart("nginx-ingress", {
    repo: "stable",
    version: "0.24.1",
    chart: "nginx-ingress",
    transformations: [addNamespace],
    namespace: "nginx",
    values: {
        rbac: {create: true},
        controller: {
            publishService: {enabled: true},
            stats: {enabled: true},
            service: {
                type: "LoadBalancer",
                externalTrafficPolicy: "Local",
                loadBalancerIP: lbIp
            },
            image: {tag: "0.24.1"}
        }
    }
}, { dependsOn: [nsnginx], provider: clusterProvider });

then this resource

const certmanagerResources = new ConfigFile("cmResources", {
    file: "<https://github.com/jetstack/cert-manager/releases/download/v0.8.1/cert-manager.yaml>", 
},{ dependsOn: [nginx, primaryPool], provider: clusterProvider });

But the ConfigFile always gets generated before the nginx-ingress Helm chart

Many thanks for the support of propagating secrets and encrypting them in the state. I have a follow-on question: how do I do this with a generated secret value? The recommendation seems to be to use the

random

module. However, using the following code, the

result

value of the

RandomString

resource is still present in plaintext in the state (even though it’s correctly hidden as an attribute of the SSM Parameter.)

let password = pulumi.secret(new random.RandomString("my-password", {
        length: 32
    }).result);

    let param = new aws.ssm.Parameter("my-password", {
        name: "/my/password",
        type: "SecureString",
        value: password
    });

I'm having trouble logging in to app.pulumi.com

I logged in to local

pulumi login --local

and now I want to login to the cloud service, but

pulumi login

keeps re-logging in to my local machine

is there any guidance on pulumi and kustomize?

Can I pass the S3 backend flags like

--acl bucket-owner-full-control

? Using Pulumi in a multi-account setup is otherwise kind of prohibitive.

Are pulumi stacks backed up?

Hi Guys, May I have a question about Pulumi / TypeScript - AWS EIP?

I'd like to set an ALB Listener rule with an

http-header

condition, but it looks like Terraform only supports

path-pattern

and

http_host

. https://www.terraform.io/docs/providers/aws/r/lb_listener_rule.html#values It looks like there are many more rules in the console for this:

In cases where Terraform is missing part of the API, what is the standard way to proceed? FYI in this case we can add that rule manually after deployment, NBD.

@swift-painter-31084 I just looked at the code in Terraform, the documentation isn't correct

It actually has no validation

so you can add any of these:

// The field in the HTTP request. The following are the possible values:
	//
	//    * http-header
	//
	//    * http-request-method
	//
	//    * host-header
	//
	//    * path-pattern
	//
	//    * query-string
	//
	//    * source-ip

but it's still way behind!

I will open an issue upstream in the morning about this

I'm trying to pass this in, perhaps the httpHeaderName is just being caught as an invalid key by TF. That is the name I pulled from a network request in the aws console.

{
            field: 'http-header',
            httpHeaderName: 'Origin',
            values: [ '*<http://snopes.com|snopes.com>*', '*snopes.local*' ],
        },

yeah they don't support that 😞

Field can only be those 2 values because of how the API needs different struct values populated