![]() ![]() To expand on this further, imagine you need to define a cluster’s infrastructure in one project and consume it from another. For individual accounts, use your account name for the organization component. Stack names must be fully qualified, including the organization, project, and stack name components, in the format //. Variables : otherOutput : Fn::StackReference : - acmecorp/infra/other - x To export values from a stack, use the following definition in the top-level of the entrypoint for your project: They can be used for important values like resource IDs, computed IP addresses, and DNS names. These outputs are shown during an update, can be easily retrieved with the Pulumi CLI, and are displayed in the Pulumi Service. Stack OutputsĪ stack can export values as stack outputs. Tags can be deleted by running pulumi stack tag rm. Once you’ve assigned an environment tag to each stack, you’ll be able to group by Tag: environment in the Pulumi Service.Īs a best practice, custom tags should not be prefixed with pulumi:, gitHub:, or vcs: to avoid conflicting with built-in tags that are assigned and updated with fresh values each time a stack is updated. For example, running pulumi stack tag set environment production assigns a custom environment tag with a value of production to the active stack. To do this, you could assign a custom tag named environment to each stack. For example, if you have many projects with separate stacks for production, staging, and testing environments, it may be useful to group stacks by environment instead of by project. ![]() Stack tags are only supported with the Pulumi Service backend.Ĭustom tags can be assigned to a stack by running pulumi stack tag set and can be used to customize the grouping of stacks in the Pulumi Service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |