feat!: if SERVICE_ENV is not set, default to dev #178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If an environment is not set, it will try to load weird paths, which might not exist in Vault Make sure SERVICE_NAME is set as a lot of paths need that to work Remove peer references as that's no longer a think BREAKING CHANGE: will exit if SERVICE_NAME is not set
Update references to the new package name. Update to go 1.21
mloberg
force-pushed
the
feature/default-env-dev
branch
from
6c6d3c9 to
ac1c521
Compare
Dbaker1298
approved these changes
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If environment is not set, it will try to load weird paths, which might not exist in Vault, so set this to a default with least privileges.
BREAKING CHANGE: will exit if SERVICE_NAME is not set