Pulumi Concepts Inputs and Outputs: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 12: Line 12:
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.


Access to the data being held onto by an Output instance must be done inside a callback, like <code>[[#apply()|apply()]]</code>, which will be called by the runtime if, and when the provider resource has the data available.
Access to the data being held onto by an Output instance must be done inside a callback, like <code>[[#apply.28.29|apply()]]</code>, which will be called by the runtime if, and when the provider resource has the data available.


Also see: {{Internal|Pulumi_Concepts#Stack_Output|Stack Outputs}}
Also see: {{Internal|Pulumi_Concepts#Stack_Output|Stack Outputs}}

Revision as of 03:36, 13 January 2022

External

Internal

Overview

The Pulumi programming model includes the concepts of Input and Output values, which model how output of one resource flow in as inputs of another resource.

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.

Access to the data being held onto by an Output instance must be done inside a callback, like apply(), which will be called by the runtime if, and when the provider resource has the data available.

Also see:

Stack Outputs

apply()

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

Input

Promise

Organizatorium

Retrieved from "https://kb.novaordis.com/index.php?title=Pulumi_Concepts_Inputs_and_Outputs&oldid=88910"