While some people coming to Pulumi are entirely new to Infrastructure as Code, increasingly teams are moving from other tools - whether cloud-specific in the form of CloudFormation or ARM Templates, or cloud-agnostic tools such as Terraform. In these organizations, new infrastructure provisioned with Pulumi must co-exist with existing resources provisioned with other tools, and often by different teams. For example, it’s common to see an application team deploying into a VPC owned and managed by a network operations team.
We’ve had a 1st class concept of encrypted secrets configuration ever since first releasing Pulumi. Customers have told us they love having such a simple and easy way to ensure safe management of tokens, database passwords, and more. Since launching, however, we’ve also heard that you’d like more control over encryption and to see this protection expanded to cover not just configuration, but all of the secret data within their Pulumi deployments.
Pulumi is the most productive tooling available today for teams building cloud applications and infrastructure, in your favorite languages. Add them together, and teams can easily take maximum advantage of Google Cloud Platform's rich features, productively, with a combined platform that makes it easy to collaborate, share, and reuse.
In this post, we’ll highlight some of the top features of Pulumi that make it a joy to work with Pulumi + Google Cloud.
The Pulumi CLI provides another way to do logging, without requiring the additional setup of these existing solutions and seamlessly integrated into your Pulumi development workflow. The
pulumi logs command provides a great first place to start for understanding your Pulumi application’s behaviour. Especially during development, this command provides direct insight into the behaviour of your application, bringing together logs across all of the different forms of compute you are using - from code running in serverless functions to containers to VMs.
- Support for Atlassian identity
- Connecting multiple identities to an existing Pulumi account
- Support for GitLab identity
Today, we are pleased to announce that we are launching support for email-based identities. You no longer need to use a social identity to sign-up for an account on Pulumi. Just fill out the signup form, and you are ready to go.
This work follows on from the support for GitLab identity and also the ability to connect identities, eliminating the need for users to create multiple accounts on Pulumi.
This helps users with repos across the major version control systems to seamlessly import their GitHub Organizations and GitLab Groups - and now Atlassian Bitbucket Teams - into a single Pulumi account. Of course, you don't need to connect identities. You can always create separate account for each of your identities, if that's what you want to do.
Creating a new Pulumi account using your Atlassian identity
To get started using your Atlassian identity, you can navigate to https://app.pulumi.com and click the Atlassian button to authenticate. If you are already logged-in to Pulumi, you should first logout and then head back to the Pulumi Console.
When you're able to build an app for any cloud using real languages, the obvious question is "Where to start?". We hear you, and so we've built some new features to help you scaffold your app and program the cloud even faster than before.