fix(api): update image version handling and remove SENTRY_RELEASE property #196
+9
−19
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.
This pull request includes changes to the
api/src
andapi/tests
directories to modify how theIMAGE_VERSION
is handled and to remove theSENTRY_RELEASE
property. The changes ensure that theIMAGE_VERSION
always starts with a 'v' prefix and simplify the configuration settings.Configuration changes:
api/src/config.py
: Modified thecheck_image_version
method to ensure theIMAGE_VERSION
starts with a 'v' prefix. Removed theSENTRY_RELEASE
property from theSettings
class. [1] [2]Usage updates:
api/src/main.py
: Updated references toSENTRY_RELEASE
to useIMAGE_VERSION
instead in the Sentry initialization and health check endpoint. [1] [2]Test adjustments:
api/tests/test_config.py
: Removed assertions related toSENTRY_RELEASE
and updated tests to reflect the new handling ofIMAGE_VERSION
with a 'v' prefix. [1] [2] [3]