![]() ![]() The modified stack can then be imported to set the current state of the stack to the new values. This is useful when manual changes need to be applied to the stack due to changes made in the target cloud platform that Pulumi is not aware of. Import and export a stack deploymentĪ stack can be exported to see the raw data associated with the 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. Look for small holes or openings on the back or the bottom of the safe. when deploying the “staging” stack of the above program, you reference the “staging” stack)įrom the infra project. Locate the back panel of the electronic element of the safe. 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 Unlike most combination lock safes, all stack-on electronic safes will come with a backup key that allows you to open the safe via a slot beneath the electronic. 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 Service. Stack OutputsĪ stack can export values as stack outputs. Tags can be deleted by running pulumi stack tag rm. Or, you can have the safe professionally drilled by a locksmith so the safe can continue to be used. If the safe is locked, you can have a locksmith retrieve the safe’s original code from the manufacture. If there is an override key you can get that key made by a locksmith. 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. If the safe is open, a new code can be set for you. 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 |