Hey all, I just made a somewhat largish change (https://github.com/pulumi/pulumi-awsx/pull/347) in

@pulumi/awsx

so that we properly pass along

providers

when creating resources there. I also made things far more consistent wrt how components and their resources are parented. I tried very hard to make it so that this should be non impactful to existing stack if you run an update after pulling this in. However, it's definitely possible I may have missed something. So if you find any of your

@pulumi/awsx

resources doing something odd during an update, please let us know asap so we can find/quash anything that unintentionally crept in. Thanks much!

Big thank you to @tall-librarian-49374 for our new post on Hosting Static Websites on Azure using Pulumi. https://blog.pulumi.com/hosting-a-static-website-on-azure-with-pulumi

For those of you in the Seattle area, join us next Wednesday for a

pulumi up

Meetup at Pulumi HQ. Invite your friends. https://www.meetup.com/Pulumi-Seattle/events/262610954/

Another great post by @tall-librarian-49374. Keep your serverless application close to your customers. https://blog.pulumi.com/globally-distributed-serverless-application-in-100-lines-of-code-infrastructure-included

For all you Stack Overflow users, we do have a

pulumi

tag. Please feel free to also post questions there. This helps make answers to common questions last and be accessible to people outside of Community Slack. We also encourage you to upvote answers and questions you find useful. https://stackoverflow.com/questions/tagged/pulumi

We now have a #docs channel! We're embarking on some serious upgrades to our docs in the coming weeks. Yesterday, we walked through all outstanding issues at https://github.com/pulumi/docs, however if you have any feedback, whether big or small -- even if it's reminding us of feedback you've given in the past -- we'd love to hear from you: head on over to #docs and we'll talk to you there!

Last week we hosted a Pulumi Meetup in Seattle. Check out my recap and YouTube links to presentations by @bitter-oil-46081 and @broad-dog-22463. 😛ulumipus-8bit: 🍕 🍻 https://www.pulumi.com/blog/pulumi-meetup-recap-apis-custom-resources-and-github-webhooks/

Last month @big-piano-35669 spoke at the NYC Kubernetes Meetup. Some of you asked if it would be recorded. Good news, it was! https://twitter.com/kubernetesnyc/status/1151257955464953856?s=21

@broad-dog-22463 helps you get started using DigitalOcean in our latest blog post. Check it out. https://www.pulumi.com/blog/getting-started-on-digitalocean-with-pulumi/

In our latest post, @breezy-hamburger-69619 walks your through Day 2 Kubernetes administration. Be sure to check out the example and tutorial. https://www.pulumi.com/blog/day-2-kubernetes-migrating-eks-nodegroups-with-zero-downtime/

Several folks have asked about the new

import

feature. More docs and blogs coming on this soon - but in the meantime - here's a video walkthrough of using import to adopt existing resources. It covers: • Deploying some "existing" Azure infrastructure (resource group, networking and VM) using Terraform • Creating a Pulumi program that describes the same infrastructure using

tf2pulumi

• Showing that by default this will create new infrastructure • Using the new

import: <id>

feature to import a resource • Highlighting how Pulumi helps ensure you correctly described the desired state of your infrastructure (so that you don't accidentally replace adopted resources) • Getting the `id`s from the

.tfstate

file • Importing the full infrastructure into Pulumi • Showing that this allows managing the resources in https://app.pulumi.com (like linking to resources in Azure Portal) • Adding a tag to the VM with Pulumi and showing that we can now make changes to the existing resource using Pulumi • Discussing how to manage

import

IDs via config in cases where there are multiple instances (dev, stage) of a deployment • Discussing when

import

can/should be removed from code once imports are complete

Today’s blog by @tall-librarian-49374 walks through 7 ways to use secret values in a .NET Core application running in Azure. Starting with natively hard-coded strings and build up from there to more secure options. https://www.pulumi.com/blog/7-ways-to-deal-with-application-secrets-in-azure/

I fiiiinally wrote up about our experience with Pulumi and how’s been a total game changer for us! https://www.codegram.com/blog/infrastructure-as-code-with-pulumi/

Thanks for the write-up. I was thinking the same thing. I love the objects, I don't like the process options available with HCL. Traditional languages give better process options.

A consistent theme we've heard from Pulumi users and customers over the last 6 months has been the importance of a stable foundation for the community to build upon. As a result, one month ago we began the process of scoping and working toward Pulumi 1.0 based on specific community and customer feedback. As part of that, we will be launching a

1.0.0-beta

release shortly, and working toward a final 1.0 release over the coming weeks for the core parts of Pulumi (the

pulumi

CLI, the deployment engine, the AWS/Azure/GCP/Kubernetes providers and the

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

service). As always, we welcome your feedback! We view 1.0 as a chance to fully stabilize the existing experience with Pulumi. We expect to follow up with 1.0.1 for additional bug fixes, 1.1 with new features for new user scenarios, and 2.0 with more ambitious changes. Moving to 1.0 will allow us to use semver for our versioning more fully. We'll be starting with the

1.0.0-beta.1

release this week, and following that up with additional betas over the coming weeks as we finalize 1.0. We do not expect significant churn in these releases, and encourage users to move from the current

0.x

releases to these

1.0.0-beta.x

releases. Those interested can follow along with the set of work that is currently considered in scope for 1.0 by following the

feature/q3

tag in GitHub at https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+org%3Apulumi+label%3Afeature%2Fq3. You can also as always follow our broader roadmap at https://github.com/pulumi/pulumi/wiki/Roadmap, which is now updated with the 1.0 plans. Pulumi has come a long way in the 2 years it's been in development, and is now used by thousands of users and hundreds of companies of all sizes. Thanks to continued feedback from everyone in the Pulumi Community, and for your help in improving all aspects of the Pulumi project!

Hot on the heels of what @white-balloon-205 said above, if you are in the Seattle area, come and join us at our launch party! https://www.meetup.com/Pulumi-Seattle/events/263808748/

Yesterday we released

1.0.0-rc.1

of the

pulumi

CLI and the core provider packages. 🎉 This 1.0 release candidate is the next step on our path toward Pulumi 1.0. Thanks to everyone for their feedback so far on the beta releases which has helped us make sure we're addressing the key things needed to deliver a stable foundation with Pulumi 1.0! I encourage everyone who can to try out the 1.0 RC and give any remaining feedback - in issues in GitHub or here in Slack.

😛ulumipus-8bit:😛ulumipus-8bit:😛ulumipus-8bit:😛ulumipus-8bit:😛ulumipus-8bit: 🎉 Today we announced the availability of Pulumi 1.0! 🎉 This is a huge milestone for Pulumi, marking an important step for completeness, stability and compatibility. It is the result 2 years of development and a wealth of feedback and learning from the Pulumi community and customers. A big "thank you" to everyone here for your engagement, feedback, and support for the Pulumi project! We've also launched a new website at https://www.pulumi.com/ along with significant improvements to docs, tutorials and reference content. Here are some of the resources and press from today's announcement for learning more about Pulumi 1.0: • "Pulumi 1.0" on the Pulumi Blog: https://www.pulumi.com/blog/pulumi-1-0/ • "Journey to Pulumi 1.0" on Joe's Blog: http://joeduffyblog.com/2019/09/05/journey-to-pulumi-1-0/ • "Pulumi takes on cloud juggernauts with flagship product for deploying infrastructure as code" on GeekWire: https://www.geekwire.com/2019/pulumi-takes-cloud-juggernauts-flagship-product-deploying-infrastructure-code/ • "Pulumi 1.0 Brings Developers and Operators Together With Modern Infrastructure as Code" on BusinessWire: https://www.businesswire.com/news/home/20190905005251/en/Pulumi-1.0-Brings-Developers-Operators-Modern-Infrastructure • "Pulumi Deepens Cloud Ties to DevOps" on DevOps.com: https://devops.com/pulumi-deepens-cloud-ties-to-devops/ And on social: • Twitter: https://twitter.com/PulumiCorp/status/1169601979774930945?s=20 • LinkedIn: https://www.linkedin.com/posts/pulumi_pulumi-10-activity-6575374750837813248-1pwR • Hacker News: https://news.ycombinator.com/item?id=20886553 and https://news.ycombinator.com/item?id=20888940 As always, your support sharing the news with your own communities is greatly appreciated!

😛artyk8s: Hot off the presses — https://github.com/pulumi/pulumi-kubernetes/releases/tag/v1.1.0 is out with Kubernetes 1.16 support 😛artyk8s:

^ does it use the new `apiVersion`s for ingress/deployment?

Hello Pulumers! Curious if anyone has written some nodejs for a step function via Pulumi?

This message was deleted.

Over the last couple months, the team at Pulumi has been working on a new policy-as-code feature that we expect to make generally available later this year. With this new Gated Deployments feature in the Pulumi Service, you can express business, compliance or security rules as functions (written in fully-expressive code!) that are executed against resources in your stacks (either individual stacks or organization wide). When policies are executed as part of your Pulumi deployments, any violation will gate or block that update from proceeding. We've been alpha testing this with a few customers, but are looking to expand the scope of feedback for a broader private beta. If you are interested, please reach out to pac@pulumi.com with your Pulumi account name, the optional organization name to grant preview access to, and details of your current Pulumi use case and interest in trialing the Gated Deployments feature. We look forward to your feedback!

We just released https://github.com/pulumi/pulumi-kubernetes/releases/tag/v1.2.0 which includes two highly-requested changes: 1. Readiness checks for Job resources - Keep in mind that you can configure the timeout for any resource using the

customTimeouts

option on the resource provider. See https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/batch/v1/#Job for additional details. 2. Automatic aliasing for different apiVersions of resources. - This should avoid the need for manual intervention as you upgrade resources with deprecated apiVersions, even if they are part of Helm charts. Happy Friday! 😛artyk8s:

Hi all, we are pleased to announce that we released https://github.com/pulumi/pulumi-vault - this will allow you to manage your HashiCorp Vault clusters with Pulumi! Thanks to @plain-businessperson-30883 for the work on this provider

We released https://github.com/pulumi/pulumi-kubernetes/releases/tag/v1.2.2 today, which should greatly improve the performance of Pulumi stacks that include many Kubernetes resources! (70+% improvement on a benchmark Istio stack we profiled) Additionally, we removed the

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

annotation that was added in version

1.2.0

. Resources that were already updated to include this annotation will not be updated to remove it, but it is no longer in use by the provider. See the changelog for full details.

Heads up that we've added a #status channel to this Pulumi Community Slack which notifies about all updates to https://status.pulumi.com/ regarding the status of the Pulumi Service. This includes notifications about status of dependent services which may or may not directly impact most Pulumi users (such as a BitBucket outage earlier today).

To celebrate Hacktoberfest (https://hacktoberfest.digitalocean.com/), we want to encourage anyone interested in contributing to the Pulumi open source projects to jump in and submit a PR, review a PR or add repros and/or additional insights to existing open issues. Any and all contributions are warmly welcomed! 🎉 We've posted a few more details on how you can participate at https://github.com/pulumi/pulumi/issues/3345. Check it out and drop us a note in #contribute if you have questions about how to get started!

Pulumi 1.4.1 is now available ... ask and you shall (often) receive! Some community requests in here including: • Lists and maps in config •

pulumi stack

renders the resource tree • Recreate specific resources with

--replace

Enjoy!