can

pulumi config

no longer show secrets?

When we find bugs, should we file them on pulumi/pulumi, or try to find (and possibly incorrectly guess) the specific module?

(re: https://pulumi-community.slack.com/archives/C84L4E3N1/p1567208954139700?thread_ts=1567142868.092900&cid=C84L4E3N1)

On large stacks (~400 resources) pulumi times out on some resources and exits, but doesn’t update the state with resources created in that time. Obviously on the next

pulumi up

it tries to created those resorces and fails as they already exist. It’s a big problem when this resource is an enabler for other resources (for example a k8s CRD controller) Is there a concurrency limit I can increase or any other way to solve this?

I want to use AWS Container Insights in a kubernetes cluster. AWS provides config yaml file. However there are some placeholders that needs to be replaced with cluster name and region. I was thinking about writing a simple async function to get the file and replace placeholders. I'm lost with types, because ConfigGroup yaml: doesn't accept a Promise. Any hints how to handle that?

Our of curiosity, how do you handle monitoring in your Kubernetes clusters? What kind of tools / setup do you use?

Hello, when I perform pulumi up to launch kubernetes and some pods, if the pod goes into retry due to some errors, pulumi up never exits. is there a way to set number of retries or timeout? It took 52 minutes and pulumi exited with the stack failure and the pod actually retried 12 times.

does anybody experience slowness of pulumi runs? Simple run with no refresh, only a single stack output variable added, with no resources unchanged per plan has been running for 10 minutes by now... I'll try to gather more debug info

Anyone have any idea how this could be solved? Have the same issue and now Pulumi apply is occasionally clearing the sub-domain record entirely.

I get the idea of convention over configuration regarding the providers (e.g. azure or kubernetes) but somehow falling back to a default like the currently logged in azure account or the active kubeconfig of the terminal looks to me like a bit of a risky thing. Sure, if pulumi is only run on CI and I locally only use test clusters this should not be an issue. But there may be the situation that one is developing some new features of a pulumi program, forgets to explicitly add the provider and pulumi falls back to the default provider which accidentally at this point in time is a current session on the production azure account. Is there an easy way to secure against such a scenario? Can I disable the default provider globally or is there a way to set the default provider to some invalid credentials on a per project (but for all stacks) basis? For the kubeconfig I could imaging setting an according

direnv

. Maybe this also works for Azure ARM env vars. But is there a better concept? If not, are there plans of doing so or are there good reasons for always having a default in place? Thanks for your help!

anyone know why my ComponentResource doesn’t output

port

, but does correctly include it in

url

?

this.hostname = service.metadata.name;
this.port = service.spec.ports.apply(
    ports => ports.find(p => p.name === "http").port
);
this.url = pulumi.interpolate`http://${this.hostname}:${this.port}/`;

this.registerOutputs({
    hostname: this.hostname,
    port: this.port,
    url: this.url
});

Is there any good reason why

pulumi preview

command hasn't got

--config

flag like a

pulumi up

has? I feel it's little bit inconsistent because

up

does preview before applying changes.

does

StackReference

work with S3 state backends?

What’s the right way to check and see if an S3 bucket already exists before I try to create it?

I know I can do

getBucket()

will

GetBucketResult

be null if I await it, if the bucket doesn’t exist?

stackReferences + S3 backend means having to store all stack states in the same bucket, requiring stacks to have unique names across stacks. I now have a stack called

cluster-infrastructure-cluster-infrastructure-dev

When I register for new account and try to run the getting started code I get could not create stack: [404] Not Found: Organization 'xx' not found anyone running into same problems?

parent

behavior when a child changes a property that should result in a replace of only the child becomes a very unintuitive tree instead. At this point it's not a replace so it also doesn't respect

deleteBeforeReplace

set on the child

(and without parent reference + how you'd expect it with parent reference too)

Can somebody explain me why this exactly manifests, is it expected behavior?

I would like to better understand what specifying a parent entails, and when you really shouldn't

Should it only be used for CustomResource wrappers then?

Not sure what to do about this error:

Error importing AWS S3 bucket policy: BucketRegionError: incorrect region, the bucket is not in 'us-east-2' region at endpoint ''

. Trying to import an existing bucket and it is in us-east-2

when using @pulumi/cloud cron() is there no way to pass a role or permissions to the function?

is there a way to force a resource to be replaced? it seems there's a bug where updating the labels of a

clusterIP

service doesn't cause a replace, instead it tries to update the service which causes an error because the

spec.clusterIP

field is immutable and set by kubernetes if not specified at creation time

Hey all…there’s a lot of Terraform documentation around VPC Peering, but I am just trying to peer 2 (or more) VPCs

getting the error: Error waiting for VPC Peering Connection to become available: Error waiting for VPC Peering Connection (pcx-043ae9555580b24da) to become available: Failed due to incorrect VPC-ID, Account ID, or overlapping

here’s my little function to do this…