Pulumi Concepts Inputs and Outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Output) |
||
| Line 10: | Line 10: | ||
An Output encodes the relationship between infrastructure [[Pulumi_Concepts#Resource|resources]] and a Pulumi application, by holding onto a piece of data and the resource it was generated from. When a consumer resource needs a piece of data generated by a provider resource, the consumer resource gets the Output of the provider resource, allowing it to know both the data value, and the provider resource it came from. This allows building a resource dependency graph, which Pulumi used to track dependencies between resources. | An Output encodes the relationship between infrastructure [[Pulumi_Concepts#Resource|resources]] and a Pulumi application, by holding onto a piece of data and the resource it was generated from. When a consumer resource needs a piece of data generated by a provider resource, the consumer resource gets the Output of the provider resource, allowing it to know both the data value, and the provider resource it came from. This allows building a resource dependency graph, which Pulumi used to track dependencies between resources. | ||
=Input= | |||
Revision as of 03:06, 13 January 2022
External
Internal
Overview
Output
An Output encodes the relationship between infrastructure resources and a Pulumi application, by holding onto a piece of data and the resource it was generated from. When a consumer resource needs a piece of data generated by a provider resource, the consumer resource gets the Output of the provider resource, allowing it to know both the data value, and the provider resource it came from. This allows building a resource dependency graph, which Pulumi used to track dependencies between resources.