Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

[bug] unable to use EnvMap for init container env #51

Open
bigkraig opened this issue Feb 4, 2020 · 0 comments
Open

[bug] unable to use EnvMap for init container env #51

bigkraig opened this issue Feb 4, 2020 · 0 comments
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@bigkraig
Copy link
Contributor

bigkraig commented Feb 4, 2020

When trying to use an EnvMap in an init container, this error is thrown:

Types of property 'env' are incompatible.
  Type '{ "test": string; }' is not assignable to type 'Input<Input<EnvVar>[]>'.
    Type '{ "test": string; }' is missing the following properties from type 'Promise<Input<EnvVar>[]>': then, catch, [Symbol.toStringTag], finally

It appears that an EnvMap is required to properly use the secret asEnvValue function to add a secret environment variable.

It may be a separate bug that asEnvValue configures the value as a value and not a valueFrom when added to a list type env.

@lukehoban lukehoban added the kind/bug Some behavior is incorrect or out of spec label Jul 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

3 participants