For folks interested in such things - there's some discussion around yesterday's Pulumi Kubernetes announcements ongoing right now on the front page of HN. These tend to be a great source of new eyes on the project, and some of the best insights and feedback on the project come from all of you in this community who are actively using Pulumi. https://news.ycombinator.com/item?id=21546099

I would think that this would work:

const
        opts = {provider: provider},
        callerId = aws.getCallerIdentity(opts),
        region = aws.getRegion({}, opts)

where provider is

new aws.Provider('myprovider', {profile: profile, region: region})

but they return

unable to discover AWS AccessKeyID and/or SecretAccessKey

has anyone created an ECS service that uses a docker image from a private registry before? I’m struggling to find where/how to define the

repositoryCredentials

property mentioned in the AWS docs (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html). I’m currently using the

FargateService

resource from AWS Crosswalk, but can’t find any reference to the

repositoryCredentials

property in the Pulumi docs for Crosswalk, nor in the source code.

Has anyone had any success integrating Pulumi with the Serverless Framework ? I think these two would be very powerful together but I don't know exactly how to integrate them. Ideally, Pulumi should do the heavy lifting while Serverless does the packaging of FaaS and the WSGI for web frameworks

Re-posting from above, does anyone know how the Pulumi GitHub app is triggered? I am using GitHub actions and it only seems to get triggered on a merge and I can't seem to get it to comment on the PR. I think I am just configuring something incorrectly but can't figure out what.

Hm just a general question, pulumi logs is marked as [PREVIEW] in the CLI docs. Does this mean it's in a testing state/not prod ready? I ask because I launched a simple s3 bucket with magic inline lambda (with console logs) to test pulumi. After pulumi up, the resources are up, and I see the console.log in cloudwatch logs (amazing!). However pulumi logs doesn't appear to be collecting the logs at all (either with -f or pulumi logs).

What is the recommended way to consume external resources (git repositories) as part of the deployment process? I am setting up a Serverless app on AWS with a static site hosted on S3. The lambdas and static site are hosted on individual repositories, and I am looking for ways to have a seamless integration between Pulumi handling the infrastructure and the deployment of those external contents. In addition, I am also looking to somehow have a continuous delivery from each lambda and static site repositories when commits are made to master. • Has anyone dealt with this already? • Are there any pitfalls to avoid? • Any reading material? Thank you

Hi Folks. How to assign the Azure directory Role to Service Principle? I try to find around the source code. But there is no sample available?

Hello Pulumi Team! I was awarded a swag hoodie in February, but it was never in my size (XXL) - checked back every few weeks. Now my link shows "This giveaway is not currently running." 😢

Hey guys, trying to set up a RDS mysql resource that requires me loading a previous backup. does pulumi have an option to do local exec like terraform or something similar?

Hi Team, I'm trying to call an AWS service using aws-sdk inside

index.ts

. It returns a promise. How can I do:

const someAwsValue = await new AWS().someService().someMethod().promise();

or similar in index.ts? Or even:

new AWS().someService().someMethod(params, (someAwsValue)=> {
   // do Pulumi things in here, referencing someAwsValue in scope
})

Pulumi won't let me wrap everything in a top-level async function without dying. I tried looking in the docs how to use aws-sdks or perform async things inside of a Pulumi project, not sure how to proceed. 😐

const p = new aws.Provider(`main-provider`, {profile: profile, region: region})

am I correct in that there is no way of getting the profile/region on p?

what is the correct procedure to upgrade a plugin to a newer version with an existing stack?

pulumi plugin rm resource gcp 1.5.0

pulumi plugin install resource gcp 1.6.0

and setting

"@pulumi/gcp": "^1.6.0"

in packages.json doesn't seem to make a difference -

pulumi up

still automatically downloads 1.5.0

Hello - Is Pulumi api service now open sourced ? so I can bring up my own API instance ?

Hi, I am getting

warning: Synchronous call made to "aws:index/getAvailabilityZones:getAvailabilityZones" with an unregistered provider.

I do not have any calls to this in my code. Would it be possible to get this warning from

new awsx.ec2.Vpc(...)

potentially?

Are the data calls cached? If I do

aws.getCallerIdentity({provider: provider})

in ten different places with the same provider will it cause 10 api calls?

Hi Guys, has anyone setup aws xray and if its currently possible? Most of the aws examples show that you pass the sdk through xray e.g

var AWSXRay = require('aws-xray-sdk-core');
var AWS = AWSXRay.captureAWS(require('aws-sdk'));

I came across this open issue: https://github.com/pulumi/pulumi-cloud/issues/46 but wanted to ask before diving deeper

Hello Pulumi team - we are faced with some “older” or “non-standard” (compared with vanilla) Kubernetes installations, i.e. with Kubernetes v1.11 provided by OpenShift 3.11. Are any possibilities in Pulumi to 1. support this versions (in terms of k8s resource versions) and 2. support specific extensions (CRD)?

is it possible to use

pulumi.stackReference

in any way without using the pulumi cloud backend (like with s3)? passing in a state file or something similar?

Using the CLI, is it possible to tell if a given stack exists? Similarly, can I check if a given stack is currently "leased"?

Just learned about pulumi. I'm kinda interested in giving it a try. Before I delve in, can it be used to provision resources on my own local linux cluster (or is it only prepped for the major cloud providers)?

Saw you guys at KubeCon/CNCFCon 👍 Going to give it a shot.

@white-balloon-205 having a problem with a pulumi stack output not working in CI/CD but does work on both command line. The stack is also visible in the web interface. How do I figure out what's going on? Not working == error: no stack named ...

Would you say Go or Dotnet was more flushed out? Seems Dotnet runtime has been released to the website but it also has a list of things still to be implemented.

I blew away a project with

rm

but now I can’t create a project with the same name. Any way to delete that project from pulumi’s state when the project doesn’t exist?

has anyone ever seen a Teraform error from Pulumi? error in thread

Are there any tips or guides for using https://github.com/pulumi/pulumi-tf-provider-boilerplate outside of the

pulumi

github org? There seem to be several references that do not get replaced by

make prepare

and I’m having a hard time getting the provider to build.

Hi all, what is the correct way to create a new Pulumi project using an existing stack? According to the output of

pulumi new --help

, we should use `--stack`:

-s, --stack string              The stack name; either an existing stack or stack to create; if not specified, a prompt will request it

However, if I do that with an existing stack, it gives an error:

$ pulumi new -n p3 --stack dev
Please choose a template: gcp-typescript             A minimal Google Cloud TypeScript Pulumi program
This command will walk you through creating a new Pulumi project.
Enter a value or leave blank to accept the (default), and press <ENTER>.
Press ^C at any time to quit.
project description: (A minimal Google Cloud TypeScript Pulumi program) 
Created project 'p3'
Enter your passphrase to protect config/secrets: 
Re-enter your passphrase to confirm: 
error: stack 'dev' already exists