Pulumi Concepts: Difference between revisions
| Line 42: | Line 42: | ||
=Inputs and Outputs= | =Inputs and Outputs= | ||
{{External|https://www.pulumi.com/docs/intro/concepts/inputs-outputs/}} | {{External|https://www.pulumi.com/docs/intro/concepts/inputs-outputs/}} | ||
=State and Backends= | =State and Backends= | ||
{{External|https://www.pulumi.com/docs/intro/concepts/state/}} | {{External|https://www.pulumi.com/docs/intro/concepts/state/}} | ||
Revision as of 21:18, 7 January 2022
Internal
TODO
Overview
Pulumi is an Infrastructure as Code platform that allows using common programming languages, tools, and frameworks, to provision, update, and manage cloud infrastructure resources. Pulumi is one of the tools that can be used to manage generic Infrastructure as Code stacks.
Pulumi vs Terraform
Also see:
Program
A program describes how the cloud infrastructure should be composed. It can be written in Python, TypeScript or Go. Infrastructure is declared by allocating resource objects whose properties correspond to the desire state of the infrastructure. It is recommended to group resource with common lifecycles together.
Supported Programming Languages
Organization
Project
Current Project
The current project is the project given by the nearest Pulumi.yaml file.
Resource
Stack
A stack is an isolated, independently configurable instance of a Pulumi program. Stacks are commonly used to denote different phases of development, such as "development", "staging" and "production", or feature branches. A project can have an arbitrary number of stacks. By default, Pulumi creates a new stack per project when pulumi new is used.
Stack Name
A fully qualified stack name includes the organization and the project name: org-name/project-name/stack-name.
Active Stack
Stack References
Stack Tags
Stacks have associated metadata as tags. Each tags has a name and a value. A set of built-in tags are automatically assigned and updated each time is updated). Tags are only supported with the Pulumi Service backend.
Stack Operations
Inputs and Outputs
State and Backends
Backend
Name
URL
Authentication and Identity
The backend decides what a user can and cannot see, for example organizations, based on user's OD group configuration. A user's OD group list, as known by the Pulumi backend, is given by pulumi whoami --verbose.