Is that possible to get the load balancer with it’s dns name?

Hey how can I get rid of the pulumi suffix when creating route53 hosted zone records?

Wanting to install the helm chart for cert-manager, I finding myself confronted with a case I didn’t encounter before : the chart declares new type of resources (

Issuer

,

ClusterIssuer

,

Certificate

, etc) that pulumi don’t know about (or at least I didn’t find the library that do) and I don’t know what to do from here. Should I create `CustomResource`s for those myself ? But if so I miss the needed knowledge to make it properly (I tried and got something kind of working but there’s things weird, like it doesn’t detect changes in the specs of some components I’ve made).

What is the origin of the name Pulumi?

Is Pulumi planning to support additional cloud provider APIs such as IBM & Alibaba?

.

Is there any documentation someone can point me to for how to setup

aws.apigateway.x.API

with a cognito user pool authorizer? The closest I've found was in this slack from @white-balloon-205 3 months ago.

In

@Pulumi/aws

I've created a Role and a Policy, and used both RolePolicyAttachment and also PolicyAttachment, but have no luck in attaching a policy to the role. What's the way to attach policies to roles?

I've exported a value from one stack. How do I import that value into a separate project?

I don't have a StackReference class in my latest pull of

@pulumi/pulumi

. Is it in a different package?

index.ts(19,27): error TS2339: Property 'StackReference' does not exist on type 'typeof import("/home/tsi/eshamay/git/mustang/sdp-mustang-terraform/pulumi/eks-cluster/node_modules/@pulumi/pulumi/index")'.

I don't have a StackReference class in my latest pull of

@pulumi/pulumi

. Is it in a different package?

No, it should be in that package. What version of the

@pulumi/pulumi

package ended up getting resolved?

How would I specify a key pair when using

infra.x.ecs.Cluster

?

How would I specify that I want a

infra.x.ecs.EC2Service

to be assigned a public IP?

It appears the default for

EC2Service

is to not assign a public IP. Because tasks are not assigned a public IP, they cannot access the internet.

I tried setting this on my

EC2Service

, but it did not work:

networkConfiguration: {
    assignPublicIp: true,
        subnets: cluster.network.subnetIds,
}

I tried stopping the task via the ECS console. It started a new task up without the public IP.

Just tried creating everything from scratch and Auto-assign public IP is still disabled.

Also tried setting

associatePublicIpAddress: true

in

launchConfigurationArgs

when calling

createAndAddAutoScalingGroup

. Still no change to the Auto-assign public IP field.

I read somewhere that Pulumi is CNCF member. What does that mean? https://docs.google.com/presentation/d/1BoxFeENJcINgHbKfygXpXROchiRO2LBT-pzdaOFr4Zg/edit#slide=id.g4730808563_31_0

Hello here. I’m having something really weird going on I can’t understand. I recently created a new stack, then I switched back to the first one to do some changes and now it seems there’s something wrong with my user :

error: Plan apply failed: ingresses.extensions is forbidden: User "REDACTED" cannot create ingresses.extensions in the namespace "default": Required "container.ingresses.create" permission.

(same problem for a

pulumi refresh

related to the permission

container.ingresses.get

) given that : - the user showed here is the right one with more permissions than needed assigned to it (

container.admin

and

editor

amongst them, which are more than enough) -

gcloud auth

and

gcloud config

show me the right account is selected - the key exported by

GOOGLE_APPLICATION_CREDENTIALS

is also the right one for this user (I even compared the id with the one in the web console to be sure) - the pulumi stack selected is the right one too I definitely have something wrong here, but I can’t spot it and I didn’t change a thing related to the service account or auth related.

I was just tinkering with Pulumi at the Node REPL and I ran into a couple discouraging issues. Is using the Pulumi JavaScript SDK in an interactive context —i.e., a console/REPL— an unsupported use case, or is it perhaps just not a priority? (Details follow; I wanted to put the TLDR up top 🙂) I’m using Pulumi 0.16.7 on macOS 10.14.2 and NodeJS 11.4.0, with both Pulumi and Node installed via Homebrew. I created a fresh project and stack with

pulumi new aws-javascript

and successfully previewed the changes. My original motivation for this was to experiment with calling the

getAmi

function to view some example result data, as well as its error behavior. My first attempt:

$ node
> const aws = require("@pulumi/aws");
{ Error: Missing required configuration variable 'aws:region'
	please set a value using the command `pulumi config set aws:region <value>`
    at Object.requireWithDefault (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/utilities.ts:45:16)
    at exports.region.utilities.requireWithDefault (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/config/vars.ts:44:78)
    at Config.require (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/pulumi/config.js:141:19) __pulumiRunError: true, key: 'aws:region' }

After some digging into Pulumi’s source code, I eventually figured out that I needed to export

PULUMI_CONFIG='{"aws:config:region":"us-east-1"}'

. I progressed to a new error!

$ PULUMI_CONFIG='{"aws:config:region":"us-east-1"}' node
> const aws = require("@pulumi/aws");
undefined
> aws.getAmi({owners: ["amazon"], filters: [{name: "name", values: ["amzn2-ami-hvm-2.*-x86_64.gp2"]}], mostRecent: true})
Promise {
  <pending>,
  domain:
   Domain {
     domain: null,
     _events:
      [Object: null prototype] {
        removeListener: [Function: updateExceptionCapture],
        newListener: [Function: updateExceptionCapture],
        error: [Function: debugDomainError] },
     _eventsCount: 3,
     _maxListeners: undefined,
     members: [] } }
> (node:15240) UnhandledPromiseRejectionWarning: Error: Pulumi program not connected to the engine -- are you running with the `pulumi` CLI?
    at Object.getMonitor (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/pulumi/runtime/settings.js:87:19)
    at Object.<anonymous> (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/pulumi/runtime/invoke.js:51:40)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/jtilles/Developer/Scratch/pulumi-experiment/node_modules/@pulumi/pulumi/runtime/invoke.js:17:58)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)
(node:15240) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:15240) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Since the second error didn’t look particularly debuggable (from the looks of it, I’m guessing I would need to launch a gRPC server in order to use the SDK from the REPL) I decided it was time to ask for help.

Is control of Mesos a part of Pulumi's plan?

Is there a way to get the default network?

Are there any higher level Pulumi resources around using CodeDeploy?

If I explicitly set the

name

on a

aws.elasticloadbalancingv2.TargetGroup

then update the

port

to a different value, I get this message:

Plan apply failed: Error creating LB Target Group: DuplicateTargetGroupName: A target group with the same name 'fibonacci-dev' exists, but with different settings
        status code: 400, request id: db1ef58c-fd8f-11e8-be77-fbf35d396053

This also occurs with

aws.autoscaling.Group

.

Changes to the

userData

of

aws.ec2.LaunchTemplate

do not trigger an update.

I have a security group defined like this:

let lbSecurityGroup = new aws.ec2.SecurityGroup("fib-lb-sg", {
    namePrefix: "fib-lb-sg",
    ingress: [{
        protocol: "tcp",
        fromPort: 80,
        toPort: 80,
        cidrBlocks: ["0.0.0.0/0"]
    }],
    egress: [{
        protocol: "-1",
        fromPort: 0,
        toPort: 0,
        cidrBlocks: ["0.0.0.0/0"]
    }],
    vpcId: network.vpcId
});

After running

pulumi up

, I get this message:

updating urn:pulumi:fibonacci-dev::fibonacci::aws:ec2/securityGroup:SecurityGroup::fib-lb-sg: from_port (80) and to_port (80) must both be 0 to use the 'ALL' "-1" protocol!

Not sure what it is talking about.

For those interested in using Pulumi to deploy your aws code in localstack for local test, here is a link to an example that I created for a lambda function: https://github.com/demiban/pulumi-localstack-lambda-example Let me know your thoughts!

error: Plan apply failed: ingresses.extensions "[ingress name]" already exists

Would you guys have any idea why pulumi does not manage properly an update of an ingress on gcp ? it seems it wants to recreate it and fails while it knows that’s an update :

+-  └─ kubernetes:extensions:Ingress           [ingress name]             **replacing failed**     [diff: ~provider]; 1 error

Did I misconfigure something ? Everything else in my cluster is working and updating as expected