You can now use the `replacementTrigger` resource option to control when resources are recreated

The Pulumi blog provides developers with resources, tutorials, and best practices for infrastructure as code (IaC) and cloud-native development using Pulumi's open-source tools. Developers can learn about deploying and managing infrastructure using familiar programming languages such as JavaScript, TypeScript, Python, and Go. Additionally, the blog covers topics such as cloud architecture patterns, multi-cloud deployments, and serverless computing, enabling developers to build and deploy modern cloud applications with ease.

Pulumi

Pulumi v3.215.0 introduces the `replacementTrigger` resource option, allowing developers to force resource recreation based on custom conditions. This feature enables use cases like cycling private keys monthly or replacing resources when external version numbers change. By attaching a value as metadata to a resource, any change in that value between updates triggers a replacement operation, regardless of other changes. The feature works by comparing the current trigger value against the persisted state, providing automated control over resource lifecycle without manual intervention or CLI flags.

New in Pulumi IaC: `replacementTrigger` Resource Option