New IO and Params option toEnv

Several users expose one or several inputs/outputs/params as environment variables in their component or operation specifications. Until now the logic required changing the container where the value needed to be exposed:

    - name: ENV_VAR_NAME
      value: '{{ value }}'

In this release, we added a new option on the inputs, outputs, or params sections called toEnv that allows users to expose the value to an env var without changing the container. Users can decide to expose the value by default when defining the inputs/outputs:

  - name: input_foo
    type: str
    toEnv: SOME_ENV_VAR_NAME # <----

Or to do it only for specific operations when they pass the param:

    value: 'This text will be available in the spec context and as an env var'
    toEnv: SOME_ENV_VAR_NAME # <----

Learn More about Polyaxon

This blog post just goes over a couple of features that we shipped in v1.12. To learn more about all the features, fixes, and enhancements, please visit the release notes and the short term roadmap.

Polyaxon continues to grow quickly and keeps improving and providing the simplest machine learning abstraction. We hope that these updates will improve your workflows and increase your productivity, and again, thank you for your continued feedback and support.