cannot use environment variable for release namespace

[ivanfetch-wt]

What happened?

I receive the following error when attempting to use an environment variable for a Helm release namespace.

Namespace "${rbacmanager_namespace}" is invalid: [metadata.name: Invalid value: "${rbacmanager_namespace}": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?'), metadata.labels: Invalid value: "${rbacmanager_namespace}": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')]

The above used this course file:

schema: v2
namespace: test
repositories:
  fairwinds-stable:
    url: https://charts.fairwinds.com/stable
namespace_management:
  default:
    settings:
      overwrite: false
releases:
  - name: rbac-manager
    namespace: ${rbacmanager_namespace}
    namespace_management:
      settings:
        overwrite: false
    chart: rbac-manager
    version: 1.11.0
    repository: fairwinds-stable

What did you expect to happen?

I expected the value for the rbac-manager release namespace to be dynamically set from the RBACMANAGER_NAMESPACE environment variable. This has worked with previous Reckoner Course schemas, also using the Python build.

How can we reproduce this?

schema: v2
namespace: test
repositories:
  fairwinds-stable:
    url: https://charts.fairwinds.com/stable
namespace_management:
  default:
    settings:
      overwrite: false
releases:
  - name: rbac-manager
    namespace: ${rbacmanager_namespace}
    namespace_management:
      settings:
        overwrite: false
    chart: rbac-manager
    version: 1.11.0
    repository: fairwinds-stable

reckoner plot -a the_above_file.yaml

Version

Go build, Version:6.0.0-rc.4 Commit:a163b28e538952188d12186b4f8a8562cc365708

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

Andy mentioned this should work and may be related to ordering of env var processing vs. namespace management, related to the Go rewrite. Here is an internal Slack thread.

[sudermanjr]

Once we merge the fix for #575, I can take a look and see if this is still an issue.

[sudermanjr]

Fixed by #576