Skip to content

Expand secrets env --env-format format choices#147

Merged
tegefaulkes merged 4 commits intostagingfrom
feature-expand-env-format
Mar 1, 2024
Merged

Expand secrets env --env-format format choices#147
tegefaulkes merged 4 commits intostagingfrom
feature-expand-env-format

Conversation

@tegefaulkes
Copy link
Contributor

@tegefaulkes tegefaulkes commented Mar 1, 2024 •
edited
Loading

Description

This PR expands the avaliable formats for polykey secrets env command's --env-format option.

Issues Fixed

Tasks

Final checklist

  • Domain specific tests
  • Full tests
  • Updated inline-comment documentation
  • Lint fixed
  • Squash and rebased
  • Sanity check the final build

@tegefaulkes
fix: reverted changes to --format and added --env-format to `secr…
11a3c99 
…ets env` command

`--format` still affects the logging format and `--env-format` is used to select the env output.

[ci skip]
@tegefaulkes tegefaulkes self-assigned this Mar 1, 2024
@tegefaulkes tegefaulkes force-pushed the feature-expand-env-format branch from 4cfe224 to 6b56ce1 Compare March 1, 2024 01:22
@tegefaulkes tegefaulkes marked this pull request as ready for review March 1, 2024 01:23
@tegefaulkes tegefaulkes merged commit 3de9266 into staging Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@tegefaulkes tegefaulkes

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Expand secrets env command formatting options

1 participant

@tegefaulkes