Possibly just me, but I had a hard time re-installing the latest pulumi on my Windows machine. I renamed the existing install and started fresh. I had to do two weird things after running the powershell script: • Run

pulumi plugin install

to get an AWS-related executable installed • Manually move

resource-aws-v0.16.2.tmp

to

resource-aws-v0.16.2

(the plugin installation kept failing with the message:

"Error: installing [resource plugin aws-0.16.2] from <https://api.pulumi.com>: rename C:\Users\Justin\.pulumi\plugins\resource-aws-v0.16.2.tmp C:\Users\Justin\.pulumi\plugins\resource-aws-v0.16.2: Access is denied.")

We've just released

v0.16.3

of

@pulumi/eks

. This release improves public vs. private subnet detection when auto-assigning worker nodes to subnets, and allows explicit specification of worker subnets instead of auto-assignment.

Greetings I have a question regarding the pulumi/vsphere plugin. I am getting this warning from Pulumi and wondering if this is fixable or indeed just a bug?

warning: resource plugin vsphere is expected to have version >=0.16.1, but has ; the wrong version may be on your path, or this may be a bug in the plugin

We've released updates to both the Pulumi CLI (now at 0.16.7) as well as many of our resource providers (aws, azure, openstack, vsphere). For folks that had not noticed, we moved to maintaining change logs for each project in their own

CHANGELOG.md

file in the root of each repository.

Hello, for those of you who were using Pulumi back in our private beta, you may recall we hosted private NPM and PyPi proxy services so you could download Pulumi packages before they were publicly available. Since our public launch (6 months ago! 🎉) the proxies haven’t been necessary, and have sat in the cloud unused. (And lonely.) The plan is to turn the proxy services down later this week. This should only impact 2-3 people, and I’ve tried to contact those folk personally. But if you encounter any errors using

pip

trying to contact

<http://pypi.pulumi.com|pypi.pulumi.com>

, just edit

~/.config/pip/pip.conf

and remove the

extra-index-url

field from which references

<http://pypi.pulumi.com|pypi.pulumi.com>

. After that, everything should work as normal. If you have any questions please don’t hesitate to ask. Cheers!

On Monday we released version

0.16.9

of the

pulumi

CLI, which includes a fix for a recent performance regression. If you've been noticing slowness during

pulumi update

operations, update to the latest release to pick up this fix (and a couple additional small improvements!). More details: https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#0169-released-december-24th-2018

When Python api docs are coming?

Heads up that a couple weeks ago we updated https://pulumi.io/reference/programming-model.html to include a fair bit more detail about Pulumi programming model topics, along with code examples in all supported languages. This is a smallish thing - but thought I'd call it out since it addresses topics that have come up many times in conversations here in the Pulumi community slack.

this is super helpful!

set the channel topic: Get your free Pulumi beanie! https://info.pulumi.com/one-quote-for-one-beanie

Hi Folks! Happy Monday! The team is happy to share that we've released 0.16.12 of the CLI. You can look at the changelog here: https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#01612-released-january-25th-2019. The major change is we've made changes on pulumi.com so that stack names now only need to be unique within an individual project instead of across an entire account. If you are using 0.16.12 of the CLI or later now, you should be able to create new stacks that have duplicate stack names across projects. Older versions of the CLI will continue to function as long as you don't duplicate the name of an existing stack. If you do, the CLI should tell you that you need to upgrade to manage that stack. The other issue is that because of the above, folks using StackReference may run into issues when doing updates, since the string you pass to the StackReference constructor now needs to change, to include the project name. Please update your use of the string to be

<owner-name>/<project-name>/<stack-name>

, e.g if I wanted to reference some outputs from the "infra-dev" stack of the "infra" project in my account, I'd do

new pulumi.StackReference("ellismg/infra/infra-dev");

When you do not specify the project name, the CLI will assume you want a stack from the current project, which is likely to be wrong. We apologize for any friction this causes. If you don't make this change, you should see errors saying that the referenced stack can't be found. You'll also notice that URLs on app.pulumi.com now contain the name of the project a stack is in. We've temporally added some re-directs such that URLs generated by older CLIs continue to work as long as you don't duplicate a stack name across your account, but these redirects will be disabled at some point, so we encourage you to update any bookmarks you might have. We'll be adding a gesture to the CLI soon to allow you to rename existing stacks, feel free to follow https://github.com/pulumi/pulumi/issues/2402 for information on that. If you notice any weirdness with the new system, please feel free to either open issues on GitHub and tag me (

@ellismg

) or reach out to me on Slack and we'll work to get you unblocked. Hopefully being able to duplicate stack names across projects will make your life better. Thank you again for using Pulumi!

We accidentally introduced a regression in the

0.16.13

version of

@pulumi/pulumi

which would cause errors of the form:

resproto.InvokeRequest is not a constructor

. This package was released earlier toady. We've already published a newer version,

0.16.14

that fixes this regression, and we apologize for any impact. We are still trying to understand how this was able to slip through our battery of tests, but wanted to get a fix out as soon as possible.

Pulumi will be featured on TGIK8s with Joe Beda today at 1pm Pacific. @creamy-potato-29402, @breezy-hamburger-69619 and I will be hanging out in chat to answer any questions. Come check it out!

Hello everyone, I’m interested in information about a partnership with Pulumi. Our team is always looking forward to using new emerging tools and we’re big on infrastructure as code. Any direction would be appreciated.

We added some new annotations that should be useful for Kubernetes users! Details are in my new blog post: https://blog.pulumi.com/improving-kubernetes-management-with-pulumis-await-logic

New blog post on Simplified Outputs in 0.17 https://blog.pulumi.com/simplified-outputs-in-pulumi-0.17.0

Really need this in python, or a mechanism for including user provided code into the async loop so that it can access Outputs in the same way.

Pulumi now supports email-based identities. https://blog.pulumi.com/announcing-support-for-email-based-identities

Hi all! We just released v0.18.0 of the GCP Pulumi Provider. Those of you tracking pulumi-gcp#57 for a while now will be happy to know that it is based on the latest release of the Google Beta Terraform provider, thus giving access to the full range of GCP resources. Because we bumped from version 1.60 of upstream to 2.2.0, there are some breaking changes, but if you are using 0.17.0 of the Pulumi CLI or above, everything should be handled correctly for you. If you notice any weirdness either around the upgrade process, or with usage post-upgrade, we’d love to hear from you so we can improve the process around taking in large changes from upstream!

Kubernetes 1.14 was just released, and we already support it with our latest provider release! https://github.com/pulumi/pulumi-kubernetes/releases/tag/v0.22.0 Fun fact: Our release actually beat the upstream release (code tagged, but not released). Thanks to the OpenAPI spec, we are generally able to pull in any changes within 30 mins of an upstream release, while providing access to the full API surface! 🎉

Hi everyone! We have just released version 0.17.4 of the Pulumi CLI, which contains a few bug fixes and new features. You can check out the changelog here: https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#0174-released-march-26-2019. The new version is available on Homebrew and https://pulumi.io/quickstart/install.html.

Does Pulumi have a concept of "unowned" resources? e.g.: I have a storage class that might exist in Kubernetes, called

ssd

. A stack that deploys with limited permissions to a namespace cannot and should not own that storage class, because storage classes are a global resource. So I'd like to conditionally choose the storage class for a volume in a statefulset with logic like:

const ssdClass = new k8s.storage.v1.StorageClass(
  'ssd', 
  { metadata: { name: 'ssd' }, ... },
  { readonly: true }, // or loadOnly, or load, or whatever, I just want to get the resource that currently exists in Kubernetes that matches the spec I've provided. if it differs, I'd like this to return undefined
);
// ... in the spec for statefulSet
   storageClass: ssdClass ? ssdClass.metadata.name : undefined`

Edit: Actually, come to think of it that API won't work,

new

will always return an instance of a class. So perhaps a static method on the Kubernetes resource, like:

k8s.storage.v1.StorageClass#read

that returns an

Output<k8s.storage.v1.StorageClass | undefined>

?

partypus 8bitIf you are heading to San Francisco Next Tuesday, be sure to say hi! https://info.pulumi.com/meet-pulumi-at-google-cloud-next

Are you familiar with the

pulumi logs

command? @white-balloon-205 gives you a quick overview and some of the ways it can be used as part of the inner loop of your Pulumi development. https://blog.pulumi.com/unified-logs-with-pulumi-logs

Are you a Python Developer? @incalculable-sundown-82514 goes into programming the cloud with Python in our latest Pulumi blog post. https://blog.pulumi.com/programming-the-cloud-with-python

Hi Folks! We released 0.17.5 of the Pulumi CLI today. For folk who are doing serverless with GCP,

pulumi logs

will now show log messages like

gcloud functions logs read

would. As always, the Changelog (https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#0175-released-april-8-2019) has a complete set of changes. Both the bits installed by default with

curl -L <https://get.pulumi.com> | sh

and

brew

have been updated. Also, for folks using GCP, much of the team will be at Google Cloud Next this week. We'll have a booth, so please stop by and say hello!

This week Pulumi is at Google Cloud Next in San Francisco. @white-balloon-205 wrote a blog post surveying what can be done using Pulumi and the Google Cloud Platform. If you’re at the conference, please stop by our booth (S1459) and say hello. https://blog.pulumi.com/pulumi-heart-google-cloud-platform

Continuing with our Google Cloud Next theme, @lemon-spoon-91807 goes deeper into using serverless with the Google Cloud Platform. https://blog.pulumi.com/simple-serverless-programming-with-google-cloud-functions-and-pulumi

Any time line on the s3/cloud storage backend? https://github.com/pulumi/pulumi/pull/2455 https://github.com/pulumi/pulumi/issues/1966

Many have inquired about testing their Pulumi programs. @big-piano-35669 covers this in his latest blog post. https://blog.pulumi.com/testing-your-infrastructure-as-code-with-pulumi