![]() ![]() ![]() getOutputDetails returns an OutputDetails object that provides direct access to the output value.This is useful when the output is used as an input to another resource. The output value can be accessed and transformed with methods like Output.apply. getOutput returns an Output that provides gated access to the output value.Stack references support two ways of reading outputs from the referenced stack: From that point onwards, Pulumi understands the inter-stack dependency for scenarios like cascading updates. Once you have that resource, you can fetch the kubeConfig output variable with the getOutputįunction. when deploying the “staging” stack of the above program, you reference the “staging” stack)įrom the infra project. In the above example, you construct a stack reference to a specific stack in this project which has the same nameĪs your current stack (i.e. The StackReference constructor takes as input a string of the form //, and lets Resources : my-stack-reference : type : pulumi:pulumi:StackReference properties : name : acmecorp/infra/other variables : stack_output : $ 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 Cloud. 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 Cloud.Ī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 Cloud 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 Cloud. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |