Able to pass context to exe/floe (to specify api)

[kbrock]

Our current workflows have the api endpoint url stored in Context["Execution"]["_manageiq_api_url"].

Before

There is no way to set the api url in exe/floe

After

./exe/floe --context '{"Execution": {"_manageiq_api_url": "http://localhost:3000"}}' workflow.asl "{}"

followup:

• [ ] https://github.com/ManageIQ/manageiq-providers-workflows/pull/73

Comments

The input changes per workflow, so it makes sense to specify alongside the workflow in the ARGV.

The api endpoint url, on the other hand, is the same across all executions, so a single value make sense.

[agrare]

@kbrock the API passing is something specific to manageiq, could you just pass the execution as part of the context input that exists already?

[agrare]

context input that exists already?

Looks like we only accept --input on the command-line and build a context from that, I think if we also had a --context option you could do floe --context '{"Execution": {"_manageiq_api_url": "http://localhost:3000"}} ...'

[kbrock]

update:

• setting context (allows a partial context)

[kbrock]

🍏 , but code climate says this is more complex. Which it is. But ensuring all these extra fields work.

[Fryguy]

I take code climate complexity with a grain of salt 😅

[kbrock]

update:

• indentation for context
• code coverage changes
• moved dev gems to gemspec
• fixed exe/floe input (legacy) - was removed by mistake

update:

• exe/floe context wording

[agrare]

@kbrock can you just update the title and description to match what we ended up doing?