Env variables are not being substituted by its actual value in commandTests about container-structure-test

[nkubala]

Hey @AlbertoSH, thanks for filing and sorry for the late reply on this one.

container-structure-test doesn't currently support environment variable substitution in the test spec itself, so you won't be able to use any env vars as part of your test args/output. However, what you're trying to do is still possible using the metadataTest:

schemaVersion: 2.0.0

globalEnvVars:
  - key: FOO
    value: test_value

metadataTest:
  env:
    - key: PATH
      value: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    - key: FOO
      value: test_value

You can specify all your env vars here and check to be sure they're set to the correct value. It's also worth noting that this will NOT let you check variables set by the OS at boot or login time, i.e. $HOME, as these are not part of the container config.

All that said, I did actually find an issue with setting the env vars outside of the CommandTests: opened an issue for that here.

[AlbertoSH]

Yes, I know that I can test the env variables with the metadataTest but my use case was more intended to check that some software was installed and its executable was added to the PATH. So my real test is something like:

schemaVersion: "2.0.0"
globalEnvVars:
  - name: "some specific software version"
    envVars:
      - key: "PATH"
        value: "$PATH:$HOME/some/dir"
    command: "someExecutableAvailableInPath"
    args: ["some", "args"]
    expectedOutput: ["Version X"]

In the end I got a similar result with:

schemaVersion: "2.0.0"
globalEnvVars:
  - name: "some specific software version"
    # PATH redefinition not needed since it's set in .bashrc
    command: "bash"
    args: ["-cl", "someExecutableAvailableInPath some args"]
    expectedOutput: ["Version X"]

But it feels like an ugly workaround

[nkubala]

@AlbertoSH this should now be supported via #130. I'll get the next release out ASAP