Use an encrypted JSON file to store configuration variables #2

Open

opened

We should be able to use a config.json file that can be encrypted/decrypted with KMS to store configuration items.

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests