Pulumi Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 45: Line 45:
=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/}}
See [[#Stack_Output|stack 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:19, 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

https://www.pulumi.com/docs/intro/vs/terraform/

Also see:

Terraform

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

https://www.pulumi.com/docs/intro/languages/

Organization

Project

https://www.pulumi.com/docs/intro/concepts/project/#projects

Current Project

The current project is the project given by the nearest Pulumi.yaml file.

Resource

Stack

https://www.pulumi.com/docs/intro/concepts/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

https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences

Stack Tags

https://www.pulumi.com/docs/intro/concepts/stack/#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 Output

https://www.pulumi.com/docs/intro/concepts/stack/#outputs

Stack outputs can be shared with other teams.

Stack Operations

Inputs and Outputs

https://www.pulumi.com/docs/intro/concepts/inputs-outputs/

See stack outputs.

State and Backends

https://www.pulumi.com/docs/intro/concepts/state/

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.

Service Backend

Configuration

https://www.pulumi.com/docs/intro/concepts/config/#configuration

Template

Secrets

https://www.pulumi.com/docs/intro/concepts/secrets/

Pulumi.yaml

Built-in Tags

pulumi:project

pulumi:runtime

pulumi:description

gitHub:owner

gitHub:repo

vcs:owner

vcs:repo

vcs:kind