Here's an initial implementation of stack output [property-name] for the orbs.
I've come to a conclusion that the priority to be able to use the output across jobs is not the responsibility of this orb. Hence I'm only setting the value to the specified environment variable inside the orb. Any other opinions about this approach is greatly appreciated!
I wasn't sure if the following flags are needed or not:
--disable-integrity-checking Disable integrity checking of checkpoint files
-e, --emoji Enable emojis in the output
--logflow Flow log settings to child processes (like plugins)
--non-interactive Disable interactive mode for all commands
--profiling string Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
-i, --show-ids Display each resource's provider-assigned unique ID
--show-secrets Display stack outputs which are marked as secret in plaintext
-u, --show-urns Display each resource's Pulumi-assigned globally unique URN
--tracing file: Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
-v, --verbose int Enable verbose logging (e.g., v=3); anything >3 is very verbose
Also, I haven't tested this approach yet so am planning to create a simple CI example for a PoC. Theoretically, it should work.
Related issue: #15
Here's an initial implementation of
stack output [property-name]
for the orbs.I've come to a conclusion that the priority to be able to use the output across jobs is not the responsibility of this orb. Hence I'm only setting the value to the specified environment variable inside the orb. Any other opinions about this approach is greatly appreciated!
I wasn't sure if the following flags are needed or not:
Also, I haven't tested this approach yet so am planning to create a simple CI example for a PoC. Theoretically, it should work.