i am having trouble after upgrading to the latest pulumi. started getting an error when using

aws.secretsmanager.getSecretVersion

where it retrieves an empty value.

I have 24 stacks in Pulumi now, I feel like thats some sort of achievement unlock or something!! lol

Hi @tall-librarian-49374, just quick question regarding to Azure AD B2C. How could we select difference Tenant when registering the application?

Hi I have one stack up and running with 2 k8 clusters with multiple helm charts deployed it. After the above stack is up, I tried to "pulumi up" on another different stack "in parallel" with same above configurations of helm charts, some of the charts are failing : "error: Plan apply failed: 2 errors occurred: * resource kibana-kibana was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'kibana-kibana' timed out waiting to be Ready * Service was not allocated an IP address; does your cloud provider support this?" any idea on what is happening?

Hey friends, I used aws CloudFormation and found out some resources was not created with CloudFormation running successfully. I am supposed this is because CloudFormation is an asynchronous service. But anyway, Is it needed to verify aws resources are really created by pulumi up ?thanks.

Hey @quaint-artist-58613, why not amazon (web) console?

@quaint-artist-58613 You could also output resource IDs and check for them on the Amazon Web Console as @nutritious-airline-70839 suggested edit : or programmatically

@nutritious-airline-70839 because it is painful and impossible when there are hundred resources.

@lively-kangaroo-29833 The resources successfully created were shown in console but the ones failed to be created were not shown in console. So comparing console events are not working.

Hey! I have a general question 😉 I know pulumi is free and open-source. If my team (4ppl) wanted to use it for production setup - what all do I have to do to "unsubscribe" from the app?

Is there any reason the pulumi docker image is so large?

Also, is there any way to disable this message when running

pulumi config set

PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions

?

Is there any reason pulumi reorders the contents of the config file when running

pulumi config set --path path.key

?

Versioning of the state file/object. Any pointers to that ?

Hi all, I'm getting an assertion failed panic during pulumi up (while previewing the update), but I'm not really sure where to start troubleshooting I'm only seeing the issue on a specific stack, so it might be an issue with the state?

Is there a way to modifiy

imported

Ressources? When I try to, it ends up looking like the screenshot and it's driving me nuts

Hi all! I'm looking for a infra-as-code tool. After a 2-week research my top two are terraform and pulumi and it's very close 😉 Have you tried terraform? Why do you use pulumi and not terraform?

https://github.com/pulumi/pulumi-kubernetes/issues/906 reported a breaking change we've been hitting on python with pulumi 1.6.x due to the unknown output preview change.

I'm having trouble pulling service values from a helm chart. Types don't complain until runtime

TypeError: Cannot read property 'status' of undefined

const grafanaChart = new helm.v2.Chart(
    "grafana",
    {
      chart: "stable/grafana",
      values: {
        service: { type: "LoadBalancer" },
        testFramework: { enabled: false }
      }
    }
  );

  cosnt grafanaHostname = grafanaChart.getResource('v1/Service', 'grafana').apply(svc => svc.status.loadBalancer.ingress[0].hostname)

What’s the best way to patch a kubernetes service account? I don’t really wish to manage it completely. i.e. to replace this shell command:

kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "registry-pull-secret"}]}' -n openfaas-fn

One thought is this

k8s.core.v1.ServiceAccount.get(
  'default',
  'openfaas-fn/default'
).imagePullSecrets.apply((pullSecrets) => {
  if (!pullSecrets.find((s) => s.name === 'registry-pull-secret')) {
    pullSecrets.push({ name: 'registry-pull-secret' })
  }
})

Is it possible to manage external helm repositories? Or is it expected that the chart be installed and updated outside the pulumi program? For instance, I have this shell script:

# Add the Jetstack Helm repository
helm repo add jetstack <https://charts.jetstack.io>

# Update your local Helm chart repository cache
helm repo update

# Install the cert-manager Helm chart
helm install \
  --name cert-manager \
  --namespace cert-manager \
  --version v0.11.0 \
  jetstack/cert-manager

https://github.com/terraform-providers/terraform-provider-aws/pull/8268 This was just approved by Terraform, so much ALB routing rules will be available soon. 🎉 When might this be integrated to Pulumi?

pulumi k8s helm refuses to deploy a helm chart with an ingress with

apiVersion "extensions/v1beta1" was removed in Kubernetes 1.16

but this will continue to be served until 1.20. Is this a bug or is there a parameter to get around this? See <https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.16.md#deprecations-and-removals>

I am seeing a bug where the minio helm chart will not install when using pulumi. It attempts to use a service account in the wrong namespace: https://gist.github.com/brandonkal/e41e159704e08638dbe5294e60232da4

Hey, My lambda needs to run pulumi cli commands for resource provisioning on the fly. I am wondering if there is library for pulumi commands ?

Hey, the team license is 225 per month up to 25 people. But my team only has 10 people. I am wondering if there a way to charge based on the exact number of team mates? I am expecting the price that is less than $225 with 10 people in my team. Thanks.

Can someone explain the following warning when running `pulumi stack ls -a -j`:

warning: 194 stacks were omitted from the results.