broad-football-5123
06/27/2019, 6:21 PMbroad-football-5123
07/02/2019, 5:22 PMpulumi up
Meetup at Pulumi HQ. Invite your friends.
https://www.meetup.com/Pulumi-Seattle/events/262610954/broad-football-5123
07/02/2019, 8:34 PMbroad-football-5123
07/09/2019, 7:02 PMpulumi
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/pulumibig-piano-35669
broad-football-5123
07/16/2019, 6:29 PMbroad-football-5123
07/17/2019, 2:15 AMbroad-football-5123
07/18/2019, 7:03 PMbroad-football-5123
07/25/2019, 4:04 PMwhite-balloon-205
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
chilly-dusk-63796
07/29/2019, 9:46 PMcrooked-jordan-34725
08/05/2019, 8:55 AMsilly-table-38618
08/05/2019, 12:33 PMwhite-balloon-205
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!broad-dog-22463
08/13/2019, 5:16 PMwhite-balloon-205
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.white-balloon-205
gorgeous-egg-16927
09/18/2019, 5:29 PMbitter-dentist-28132
09/19/2019, 5:18 PMnice-airport-15607
09/25/2019, 5:14 PMsparse-intern-71089
09/26/2019, 9:43 PMwhite-balloon-205
gorgeous-egg-16927
10/04/2019, 9:44 PMcustomTimeouts
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! partyk8sbroad-dog-22463
10/07/2019, 5:40 PMgorgeous-egg-16927
10/10/2019, 11:32 PM<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.white-balloon-205
white-balloon-205
chilly-crayon-57653
pulumi stack
renders the resource tree
• Recreate specific resources with --replace
Enjoy!white-balloon-205
chilly-crayon-57653