since due to how our function normally accepts strings...in this case I'd need it to accept Pulumi.output<string>

although I got similar errors when hard coding my name and a co-workers in the members param

testing to see if it's a collision between IAMBinding and IAMMember

Any idea why this would happen?

Preview failed: refreshing urn:pulumi:services-prod::services::aws:ecr/repository:Repository::pulum-1111111-container: timeout while waiting for state to become 'success' (timeout: 1m0s)

In fact, if I run

pulumi refresh

on my stack, ECR previews all fail.

According to the AWS status page, ECR is operating normally.

The `aws:ecr:Repository`s timeout and `aws:ecr:LifecyclePolicy`s continually say "refreshing".

Hi, I created a redis with

aws.elasticache.ReplicationGroup

, it looks like the cluster name will be the

replicationGroupId

field value, which is not auto generated and a required field, because of this, when I changed the code, pulumi was unable to create the new resource first, because

aws:elasticache:ReplicationGroup (dlv-sbx-redis-ch):
    error: Plan apply failed: Error creating Elasticache Replication Group: ReplicationGroupAlreadyExists: Replication group with specified name already exists.
        status code: 400, request id: 4db05f24-ecb5-11e8-9c78-b503b112c20a

Is it possible to let pulumi handle the naming in this case too? Or maybe the

deletetBeforeCreate

should be used

is there any way to run a one-off command when a certain resource changes?

Hey, is there a way that I can get the storageclass name? I notice pulumi will create the storageclass name as

<cluster>-gp2

instead of just

gp2

, which I need to specify the storageclass in some of the helm deployment.

https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/s3/#property-websitedomain-2 This is only resolving to s3-website-$region.amazonaws.com. for me

not sure if thats also the default behaviour of the terraform provider

otherwise i think its a bug

Do I have any options for adopting existing AWS infrastructure into Pulumi, or do I have to wait for #1635 / #1662 to finish in 0.18+?

I don’t need code autogeneration, I’d be happy with the Terraform way of defining my resources and importing new state from AWS that my code matches.

How would I specify the

healthCheck

param [1] on a

cloudAws.Service

container? [1] https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_healthcheck

semi-off-topic but for those of you doing Pulumi/K8s - what's a good baseline for creating/understanding the RBAC role an application should have in its namespace?

Anyone know where I might find an example on pulumi utilizing aws elastic beanstalk? I found api docs but turning up nada in the GitHub examples folder in repos

I just created a

new aws.cloudwatch.MetricAlarm

with

dimensions: [{VpnId: "..."}]

. Creating the Alarm with Pulumi ends up in a wrong formatted dimension. Can you verify that this a bug or a wrong dimensions definition on my side?

Having issues installing plugins ...

pulumi plugin install resource aws v0.16.3-dev.1542649495
[resource plugin aws-0.16.3-dev.1542649495] installing
error: [resource plugin aws-0.16.3-dev.1542649495] downloading from <https://api.pulumi.com>: failed to download plugin: [404] 404 page not found

any one else seeing the same issues?

Hey guys, everytime I try to update my ECS stack I get a timeout after 10 minutes. Doesn't matter how I set it up, the initial run goes well but every update after results in a timeout:

Diagnostics:
  aws:ecs:Service (django-app-worker):
    error: Plan apply failed: 1 error occurred:

    * updating urn:pulumi:backend-dev::django-deploy::cloud:service:Service$aws:ecs/service:Service::django-app-worker: timeout while waiting for state to become 'true' (last state: 'false', timeout: 10m0s)

  aws:ecs:Service (django-app):
    error: Plan apply failed: 1 error occurred:

    * updating urn:pulumi:backend-dev::django-deploy::cloud:service:Service$aws:ecs/service:Service::django-app: timeout while waiting for state to become 'true' (last state: 'false', timeout: 10m0s)

Any idea where to start debugging this issue?

I've done the following and not sure how to fix it: 1) Created a project 2) Created a stack 3) Deleted the project code in an unrecoverable way 4) Can't figure out how to delete the stack Any pointers? Is there a console way to delete it?

What's the difference between

cloud-aws:ecsAutoClusterInstanceRolePolicyARNs

and

cloud-aws:computeIAMRolePolicyARNs

?

I'm trying to spin up a simple node rest API server in lambda. I'm familiar with node and pulumi, but not so much with Lambda. Is there a sample already out there showing the pieces needed to do this?

Hopefully abstracting all the lambda stuff so I can just deal with coding the way requests are handled

Hi guys, I am trying to create a gcp service account and a k8s secret associated to it via pulumi but am failing with two issues * I am unable to create a IAM binding to the service account using the role

roles/storage.admin

(whats also weird is that using

roles/editor

works). Using

gcloud projects add-iam-policy-binding ...

however works as expected and the storage admin role is associated * I can't get the

k8s.core.v1.Secret

class to accept the created service account key as the data for the secret I am using the following code, any help is greatly appreciated!

js
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
import * as k8s from "@pulumi/kubernetes";

const gcloudProjectId = '...'
const resourceName = "team-v1-tyll-kaniko";
const serviceAccount = new gcp.serviceAccount.Account(`${resourceName}`, {
  accountId: "team-v1-tyll-kaniko",
  displayName: "team-v1-tyll-kaniko",
  project: gcloudProjectId
});

const serviceAccountKey = pulumi
  .all([serviceAccount.email, serviceAccount.project])
  .apply(([email, project]) => {
    return new gcp.serviceAccount.Key(`${resourceName}-key`, {
      serviceAccountId: `projects/${project}/serviceAccounts/${email}`
    });
  });

const serviceAccountBinding = pulumi
  .all([serviceAccount.email, serviceAccount.project])
  .apply(([email, project]) => {
    return new gcp.serviceAccount.IAMBinding(`${resourceName}-binding`, {
      // Throws with Role roles/storage.admin is not supported for this resource.
      // role: "roles/storage.admin",
      role: "roles/editor",
      serviceAccountId: `projects/${project}/serviceAccounts/${email}`,
      members: [`serviceAccount:${email}`]
    });
  });

const secret = new k8s.core.v1.Secret("kaniko-secret", {
  type: "generic",
  metadata: { name: "kaniko-secret" },
  data: {
    // Throws with ObjectMeta: v1.ObjectMeta: TypeMeta: Kind: Data: decode base64: illegal base64 data at input byte 17, parsing 205
    "kaniko-secret": serviceAccountKey
  }
});

hi, ive a a problem with the aws dms modules, when i created a s3 endpoint target with extraConnectionAttributes, its not set on the dms aws s3 endpoint but the endpoint is well created

const s3EndpointTarget = new aws.dms.Endpoint('my-dms-endpoint', {
  engineName: 's3',
  endpointId: 'my-dms-endpoint,
  endpointType: 'target',
  serviceAccessRole: 'arn:aws:iam::xxxxxx:role/dms-replication',
  extraConnectionAttributes: 'addColumnName=true;compressionType=GZIP;csvDelimiter=,;csvRowDelimiter=\n',
  s3Settings: {
    bucketName: 'my-s3-bucket',
    ServiceAccessRoleArn: 'arn:aws:iam::xxxxx:role/dms-replication',
  },
});

if someone have an idea ?