Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENV resource from file #349

Open
fawadasaurus opened this issue Jul 3, 2023 · 0 comments
Open

ENV resource from file #349

fawadasaurus opened this issue Jul 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@fawadasaurus
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, the application has access to all environment variables. This is not ideal as all other resources are explicitly defined ahead of time. This is also valuable in deployment scenarios where a single secret can be stored and mounted as a filesystem directory instead of passing multiple individual secrets as environment variables to each deployed container.

Propose a solution
Environment variables should have a resource definition just like ports and file system.

resources:
  - name: env
    resource:
      kind: wick/resource/environment@v1
      vars_from:
        file:
          - .env
          - /root/.zshrc
        env:
          - ABC
          - MY_ENV_VAR

Describe alternatives you've considered
None

Additional context
None

@fawadasaurus fawadasaurus added enhancement New feature or request triage To be triaged labels Jul 3, 2023
@jsoverson jsoverson removed the triage To be triaged label Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants