Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add AWS KMS support to SignerStore #452
Add AWS KMS support to SignerStore #452
Changes from 3 commits
cf430d7
c4b26c0
c3ff903
60e7514
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You said this was done to allow re-using the Dynaconf setting name. Could you give an example where it's possible for
ONLINE_KEY_DIR
name to be reused?I thought we want to try and keep all
RSTUF
related env variables with theRSTUF
prefix.PS: In your changes in
docs/source/guide/Docker_README.md
line 230 we describe with its full nameRSTUF_ONLINE_KEY_DIR
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
ONLINE_KEY_DIR
is not reused. Only theRSTUF_AWS*
ones, which are AWS common env variables.Dynaconf uses
RSTUF_
, the prefix, to identify the environment variables it adds to the Dynaconf settings.All are still
RSTUF_
, but only inside the function, the usage, theRSTUF_
. Dynaconf automatically removes it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then why do we rename it here to
ONLINE_KEY_DIR
only when the full name under which you can find it isRSTUF_ONLINE_KEY_DIR
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't get your question.
On the OS/Container we need to use the
RSTUF
:root@3f79f6f8a407:/opt/repository-service-tuf-worker# env | grep RSTUF RSTUF_AWS_ACCESS_KEY_ID=test RSTUF_AWS_ENDPOINT_URL=http://localstack:4566 RSTUF_BROKER_SERVER=redis://redis/1 RSTUF_SQL_SERVER=postgresql://postgres:secret@db:5432 RSTUF_REDIS_SERVER=redis://redis RSTUF_AWS_SECRET_ACCESS_KEY=test RSTUF_STORAGE_BACKEND=AWSS3 RSTUF_AWS_STORAGE_BUCKET=tuf-metadata RSTUF_AWS_DEFAULT_REGION=us-east-1
But, in the Dynaconf it is used only to map these as settings used by Dynaconf
But it is not the one you use to map in Dynaconf.
We use
RSTUF_*
in docs for the user (Docker_README) but not in the code itself.