feat: default service-key for single tenant #420
Merged
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.
What kind of change does this PR introduce?
Feature
What is the current behavior?
Currently, the
TENANT_ID
,SERVICE_KEY
,REGION
andANON_KEY
env variables are required to run storage in single-tenant modeWhat is the new behavior?
the
SERVICE_KEY
env is now optional.When not provided, the service will generate one at boot time using the
AUTH_JWT_SECRET
SERVER_REGION
is now optional, and only used in metrics. (defaultnot-specified
)STORAGE_S3_REGION
is used as the aws region (defaultREGION
)the
TENANT_ID
env is now optional defaulting tostorage-single-tenant
ANON_KEY
is now deprecated as the service is not currently using itAdditional context
This PR will simplify even further self-hosting for storage
Example Docker Compose to launch storage in single tenant: