Source environment variables from `.env` file when adding deployment secrets

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cli, security

Research direction

Start at the krane secrets add CLI entry point and inspect how deployment secrets are currently collected and uploaded. Use the .env example in the issue to define the expected invocation and output; done means variables are sourced from the file and existing secrets are reported without being overridden.

Written by the indexing model from the issue text.

Description

enhancement

Currently, setting secrets is a very manual process and can be streamlined using a users .env file. The .env file can be referenced in the command line so that they get sourced and uploaded as secrets.

$ krane secrets add my-deployment -f ./.env

If an environment variable defined in the .env ALREADY exists it should not be overridden

Done uploading secrets for my-deployment sourced from ./env:
DB_URL: @DB_URL
DB_USER: @DB_USER

We found some secrets which where already in use and not overriden:
DB_PASSWORD: @DB_PASSWORD
Dominant language
TypeScript
Stars
1
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from krane/cli

All issues in krane/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.