Hey folks, I'm attempting to recycle the username and password on a RDS cluster here, but when it does pulumi is attempting to create the db from scratch and then fails due to the DB already existing

is there anyway around this

Hello everyone 👋 New Pulumi customer here. Loving the toolkit so far.

[EDIT: Corrected timing - the link below is also correct] I'll be hosting an office hours today at 4PM PDT / 10 AM AEDT / 11PM GMT. Feel free to stop by! https://pulumi-community.slack.com/archives/C0110AVM89Z/p1616490643005300

How long does the Pulumi CLI cache new project(s), I was creating a new project - it failed with a permissions error (I'll ask about that separately). After I wiped out the directory, the CLI is still telling me there's already a project created with that name.

Hi! Yesterday I started using Pulumi, followed the workshop. I really like it so far! Planning on migrating all my Terraform plans to Pulumi.

Bumping into a problem with

Promise leak detected

. I have my subclass of ComponentResource for a certain k8s abstraction, containing 2 resources. I pass the

args

unchanged to the second resource. As a bug in my code, I forgot to pass

args.metadata

to the first of my contained resources, mainly to have the correct k8s namespace for this resource as well. But after passing the metadata, I get the

Promise leak detected

. Below is a summary of my component:

export class Service extends pulumi.ComponentResource {

    constructor(name: string, args: kubernetes.core.v1.ServiceArgs, opts?: pulumi.ComponentResourceOptions) {
      super("ng:kubernetes:core:Service", name, {}, opts);
  
      this.backendcfg = new backendconfig.cloud.v1.BackendConfig(
        `${name}-backendconfig`,
        {
          metadata: args.metadata,
          ...
        },
        {
          parent: this,
        }
      )
  
      this.service = new kubernetes.core.v1.Service(
        name,
        args,
        ...
      );
  
  }

Hey, what about importing resources created with custom resource providers? According to this GH issue: https://github.com/pulumi/pulumi/issues/3550#issuecomment-557216373 it's still a problem?

Hi all, I'm seeing issues with 403s while installing plugins (looks like S3 permissions on Pulumi's end). I've opened up an issue https://github.com/pulumi/pulumi/issues/6610.

Hi, we use Pulumi a lot at our organisation and feel quite useful and interesting. Now that we thought we could take advantage of Pulumi Kubernetes Operator and drive stacks backed by Pulumi self-managed backend hosted on Azure Blob storage. When we try to update an existing stack from a repo, we get *unable to open bucket azblob://*****: azureblob.OpenBucket: accountName is required* as we couldn't get AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_KEY environment variables during stack update. Does anyone know how to make these env variables available before or when operator tries to select the existing stack and update the stack?

Hi all, I have a question, and I think it is an easy one, and that I am just being very dumb. I have tried a few different little projects. I am just using

pulumi login --local

. These two projects are in different folders, with different yaml files. Each had their own stack created, but when I say

pulumi stack ls

in one of the projects folders, I seem to get both stacks accross multiple projects. I noticed this only because I tried to name the stack in both projects "dev". Am I doing something wrong here, or is this a byproduct of using local login or something?

question, the https://www.pulumi.com/pricing/ plan comparasion, says that starter plan has "Up to 20 Project stacks" Does this means that a single project can have maximum 20 stacks, or that across all projects we can have maximum 20 stacks? Also on the free plan this is not specified, does the same limit applies or another?

Hello everybody, I have a question about pulumi output. In my project, I am deploying infrastructure on AWS. I want to use "address" output from RDS instance, and use that as environment variable for ecs container definition. However, it seems that I cannot extract string from address output.

I've tried to do something like this master.address.apply(lambda ad: "{ad}") but it's not working. I'am using Python

Can you guys help me?

Hey, I've run in to an issue where I can't see one of my stacks with

pulumi stack ls

unless

PULUMI_CONFIG_PASSPHRASE

is set, I'm using the s3 backend and the passphrase secrets provider. Output of

pulumi --logtostderr -v5 stack ls

below:

I0324 18:37:18.745036   38931 backend.go:859] error reading stack: staging (decrypting secret value: failed to decrypt: incorrect passphrase, please set PULUMI_CONFIG_PASSPHRASE to the correct passphrase) skipping
NAME         LAST UPDATE  RESOURCE COUNT
management*  3 weeks ago  32

Does anyone have any ideas? I can't

pulumi up

right now because there's a reference to the staging stack and the passphrase is different 😅

yeah, I came across this... your passphrases need to be the same for the stack references to work.

Helllo I have an error with GCP

error: gcp:container/cluster:Cluster resource 'cluster_infratotal' has a problem: Computed attribute cannot be set

Hello, I am really puzzled by the kubernetes provider. I am trying to deploy Traefik using the helm chart in Go. The namespace is not created automatically, so I am creating it and throwing a DependsOn ResourceOption. What I have noticed is that not all resources are created in the namespace: the Service isn’t. Could it be because they are using the new List kind?

# Source: traefik/templates/service.yaml
apiVersion: v1
kind: List
items:
  - apiVersion: v1
    kind: Service
    metadata:
      name: traefik
      labels:
        <http://app.kubernetes.io/name|app.kubernetes.io/name>: traefik
        <http://helm.sh/chart|helm.sh/chart>: traefik-9.18.0
        <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
        <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: traefik
      annotations:
    spec:
      type: LoadBalancer
      selector:
        <http://app.kubernetes.io/name|app.kubernetes.io/name>: traefik
        <http://app.kubernetes.io/instance|app.kubernetes.io/instance>: traefik
      ports:
      - port: 80
        name: web
        targetPort: "web"
        protocol: "TCP"
      - port: 443
        name: websecure
        targetPort: "websecure"
        protocol: "TCP"

Hello, I am not sure what happened but one of our stacks is gone. I was wondering if there's a way to recover it from the backups (We use S3 as backend for state) I've downloaded the file but the import command doesn't work

error: could not deserialize deployment: unexpected end of JSON input

Yet another interesting case 🙂

trying to remove resource which does have child one, it says remove child at first, but when trying to do that it says it doesn't exist 🙂

Hi, My token expired during a pulumi up and it failed. Then my eks cluster got created but pulumi did not see it. I did a refresh, which complains so I remove the eks creating from stack export. And do a stack import. Now the stack does not have knowledge of the eks cluster. So when I do a pulumi up, this fails because the cluster has already been created. What can I do from there to have a successful pulumi up? And did I do something wrong when removing the ongoing operation in the export. Should I have changed it to ‘created’?

Hi so switching to a local backend seems quite simple:

pulumi login --local

However I'm unclear on how to switch back again as this doesn't seem as simple. I'm currently at:

pulumi logout; pulumi login

Manage your Pulumi stacks by logging in.
Run `pulumi login --help` for alternative login options.
Enter your access token from <https://app.pulumi.com/account/tokens>
    or hit <ENTER> to log in using your browser                   :

Open the browser, login to pulumi.com, create a new token, paste it into the terminal. I already have a login and token so why is this needed? Is there something as simple as switching to a local backend? e.g.

pulumi login --standard

Hello, has pulumi the management for ClusterIssuer on Kubernetes ?

Hello guys! I am new to Pulumi, and I want to understand the best approach to tackle my use case, Currently I have an IAM project with 10 stacks, and there is an automation for applying the changes that are made there. each change in the project leads to 7 minutes that the cloud build runs because it going over each stack by order. - Which is a lot of time for updating permissions A suggestion came up in my team to merge all the stacks to 1 file, so the "pulumi up" will supposedly run only once, and by that the apply time will shorten Is that possible? And is there a better approach to that?

Hello, I have an issue trying to import a DB Instance from GCP

pulumi import gcp:sql/databaseInstance:DatabaseInstance db_instance projects/mystical-moon-307818/instances/prod-mysql

Error

gcp:sql:DatabaseInstance (db_instance):
    error: gcp:sql/databaseInstance:DatabaseInstance resource 'db_instance' has a problem: AtLeastOne: "settings": one of `clone,settings` must be specified
    error: gcp:sql/databaseInstance:DatabaseInstance resource 'db_instance' has a problem: AtLeastOne: "clone": one of `clone,settings` must be specified
    error: Preview failed: one or more inputs failed to validate