Ability to access Pack Config from orquesta workflow

SUMMARY

Currently if a user wants to access pack config data from an Orquesta workflow, the user must add an additional parameter to the action definition, set it to a default of {{ config_context.xxx }} and pipe it into the workflow.

---
name: "send_sms"
runner_type: "python-script"
description: "This sends an SMS using twilio."
enabled: true
entry_point: "send_sms.py"
parameters:
    from_number:
        type: "string"
        description: "Your twilio 'from' number in E.164 format. Example +14151234567."
        required: false
        position: 0
        default: "{{config_context.from_number}}"

It would be great if the pack's config was available in the workflow definition itself. This would allow users to do interesting this like accessing config keys based on output of actions.

I think it makes sense that the "config" in this case would be the config for the pack that the workflow resides in.

ISSUE TYPE

• Feature Idea

MOCK WORKFLOW

version: 1.0

description: A basic workflow that runs an arbitrary linux command.

input:
  - cmd
  - timeout

tasks:
  task1:
    action: core.local cmd=<% ctx(cmd) %> timeout=<% ctx(timeout) %>
    next:
      - when: <% succeeded() %>
        publish:
          - stdout: <% result().stdout %>
          - stderr: <% result().stderr %>

  task2:
   # accessing the pack's config here
    action: core.local cmd="ls <% config(ctx(stdout)) %>"
    next:
      - when: <% succeeded() %>
        publish:
          - data: <% result().stdout %>

output:
  - stdout: <% ctx(data) %>

Start by reading the Orquesta workflow definition and the existing config_context parameter flow described in the issue. Compare the mock workflow's desired config access with the current action-definition workaround. Done means pack configuration is available from workflow expressions, including values selected using action output.