2021-11-08 16:04:20 -06:00
|
|
|
---
|
2023-03-14 11:25:48 -07:00
|
|
|
title_tag: Understanding Stacks | Learn Pulumi
|
2021-11-08 16:04:20 -06:00
|
|
|
title: "Understanding Stacks"
|
|
|
|
|
layout: topic
|
|
|
|
|
date: 2021-09-20T08:33:14-05:00
|
|
|
|
|
draft: false
|
|
|
|
|
description: Learn a bit more about stacks as part of using Pulumi.
|
2023-03-14 11:25:48 -07:00
|
|
|
meta_desc: Learn what a stack is, how stacks work within Pulumi, and how to create, list, and select stacks in this tutorial.
|
2021-11-08 16:04:20 -06:00
|
|
|
index: 1
|
|
|
|
|
estimated_time: 10
|
|
|
|
|
meta_image: meta.png
|
|
|
|
|
authors:
|
|
|
|
|
- matt-stratton
|
|
|
|
|
tags:
|
|
|
|
|
- stacks
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
Every Pulumi program is deployed to a stack. A stack is an isolated,
|
2023-05-15 15:25:28 -07:00
|
|
|
independently [configurable](/docs/concepts/config/)
|
2021-11-08 16:04:20 -06:00
|
|
|
instance of a Pulumi program. Stacks are commonly used to denote different
|
|
|
|
|
phases of development (such as `development`, `staging`, and `production`) or
|
|
|
|
|
feature branches (such as `feature-x-dev`).
|
|
|
|
|
|
|
|
|
|
A project can have as many stacks as you need. By default, Pulumi creates a
|
|
|
|
|
stack for you when you start a new project using the `pulumi new` command.
|
|
|
|
|
|
|
|
|
|
## Create a stack
|
|
|
|
|
|
2022-12-19 15:43:21 -07:00
|
|
|
To create a new stack, we use the command `pulumi stack init name`. This
|
|
|
|
|
command creates an empty stack `name` and sets it as the _active_ stack.
|
2021-11-08 16:04:20 -06:00
|
|
|
The project that the stack is associated with is determined by finding the
|
|
|
|
|
nearest `Pulumi.yaml` file.
|
|
|
|
|
|
|
|
|
|
The stack name must be unique within a project. Stack names may only contain
|
|
|
|
|
alphanumeric characters, hyphens, underscores, or periods.
|
|
|
|
|
|
|
|
|
|
Let's create a new stack in our project, for our staging environment:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
$ pulumi stack init staging
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Listing stacks
|
|
|
|
|
|
|
|
|
|
We have a couple of stacks in our project now—but how do we know which
|
|
|
|
|
ones we have? If we run the command `pulumi stack ls`, it will tell us!
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
$ pulumi stack ls
|
|
|
|
|
NAME LAST UPDATE RESOURCE COUNT URL
|
|
|
|
|
dev 2 minutes ago 10 https://app.pulumi.com/***/my-first-app/dev
|
|
|
|
|
staging* n/a n/a https://app.pulumi.com/***/my-first-app/staging
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Notice that the `staging` stack has an `*` after its name; this asterisk marks
|
|
|
|
|
this stack as the active stack (i.e., the stack that all our commands will run
|
|
|
|
|
on).
|
|
|
|
|
|
|
|
|
|
## Selecting stacks
|
|
|
|
|
|
|
|
|
|
When we run a Pulumi command (such as `config`, `up`, or `destroy`), the command
|
|
|
|
|
operates on the *active* stack. But what if we want to change which stack is
|
|
|
|
|
active? For this task, we use the `pulumi stack select` command:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
$ pulumi stack select dev
|
|
|
|
|
|
|
|
|
|
$ pulumi stack ls
|
|
|
|
|
NAME LAST UPDATE RESOURCE COUNT URL
|
|
|
|
|
dev* 3 minutes ago 10 https://app.pulumi.com/***/my-first-app/dev
|
|
|
|
|
staging n/a n/a https://app.pulumi.com/***/my-first-app/staging
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Notice that `dev` is now the active stack.
|
|
|
|
|
|
|
|
|
|
Next up, we're going to explore how to get information out of a stack to use in
|
|
|
|
|
other places, like elsewhere in our program or in general spots like your
|
|
|
|
|
browser.
|
