bug: env vars are not set as uppercase

[chrisjohnson00]

Given a YAML file structured as such:

features:
  ghcr:
    enabled: true

Using the following with on the action:

        with:
          file-path: '.github/docker_build_settings.yaml'
          separator: '_'
          export-env-variables: true

The resulting env var is:
features_ghcr_enabled=true

General standard is for env vars to be upper case.

[joernott]

In my opinion, this is not a bug but a feature. Upper case env variables are a leftover from the 1970s ;-) Being a relic born in that centuy, I still tend to set my bash variables to all caps. Howerver, I started to adapt.
What stops me from writing a yaml lile

FEATURES:
  GHCR:
    ENABLED: true

if I want to have the variable FEATURES_GHCR_ENABLED instead of features_ghcr_enabled?

[mknet3]

it can be a feature but without breaking the existing behavior. e.g. adding a flag to export variables as uppercase could help. What do you think @chrisjohnson00 @joernott ?

[chrisjohnson00]

it can be a feature but without breaking the existing behavior. e.g. adding a flag to export variables as uppercase could help. What do you think @chrisjohnson00 @joernott ?

It could be set as a variable or set as both original case and all upper by default.
But honestly, this is not an important issue by any measure.