👋I’m Tasia, a Computer Science student at the University of Washington and Pulumi’s very first intern. Read on to learn about some of my thoughts and experiences from these past few months! Why Pulumi? I’ve interned at a few different companies before, but for my last internship, there were several things I was looking for: A start-up. All the companies I worked at previously had at least a couple thousand people, and I wanted to see first-hand the difference in both engineering and culture between larger, more established companies and smaller, newer ones.
We’ve been hard at work making it easier to manage stacks, permissions, and organizations in the Pulumi Console. Adding new features like first-class support for stack tags, deep links into CI/CD providers, and downloadable checkpoint files.
In this post, we showcase what’s new!
“What’s in a name? That which we call a rose by any other name would smell as sweet.” William Shakespeare’s oft repeated quote was used to help Juliet explain that a “Montague” is worthy of love. Juliet may have underestimated the importance of a name, however, since things didn’t work out so well for everyone in Verona! Many customers have questions about “names” in Pulumi – and in an effort to make sure that things work out better for them than they did for Romeo, here’s a quick note on naming!
Just over a month ago we publicly launched Pulumi, a new cloud native development platform. The response has been overwhelming and we’ve been hard at work responding to your feedback ever since. Today, we are excited to release Pulumi 0.15 and make it available to download. This release includes improvements across the entire Pulumi development experience. Pulumi supports more platforms (Kubernetes and OpenStack), is faster (Parallelism, simpler (native TypeScript support), richer (serverless frameworks for Azure and GCP), and is more deeply integrated into the application lifecycle (GitHub App for CI/CD integration).