https://cloudposse.com logo
Join Slack
Powered by
Any opinion on `choice` options being determined a...
# atmos-dev
b
Any opinion on 
choice
options being determined at runtime? I would like to populate the options for 
choice
in earlier step prior to reaching the step. Related, any opinion on 
markdown
not being pre-render before any 
steps: []
are executed? I would like to render 
.steps.<name>.output
in markdown using 
markdown
type.
e
Yes, that would be neat
How would options get populated? Can you propose a syntax?
Sounds like a bug if the markdown is rendered before steps are executed
b
I honestly hadn't spent much time on the it. Ideally, I would like to use 
options
contract but requires an array but 
.steps.<name>.output
is a string. Therefore might need to introduced 
options_from
or similar that allows for the input for both the delimited string and delimiter itself. I am open to other ideas. As for 
markdown
, Ill reconfirm if it is a bug and submit a PR if so.
e
maybe 
.output
can be serialized / json
What would be your "generator" that produces the output?
b
Ill get back to you on the dynamic options for 
choice
. I want address the possible 
markdown
bug.
github.com/cloudposse/atmos/issues/2781 - Can you confirm if this is bug? It doesn't pre-render as expected. It's just 
shell
or 
atmos
types of steps, never store its outputs. The new steps that were added with the interaction commands and steps do store the outputs. Therefore, the stored output can be referenced via 
{{ .steps.<name>.value }}
.
If confirmed, Ill submit a PR to fix then turn my focus back to dynamic options.
I know why 
{{ .steps.<name>.value }}
does not work for 
shell
steps. My real question is it expected behavior.
2 Views
Open in Slack
PreviousNext
Powered by