-
Notifications
You must be signed in to change notification settings - Fork 429
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
fix(versioning): handle mapping of environment to engine post v2 versioning migration #3913
fix(versioning): handle mapping of environment to engine post v2 versioning migration #3913
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3913 +/- ##
==========================================
+ Coverage 95.94% 95.98% +0.04%
==========================================
Files 1135 1135
Lines 36087 36170 +83
==========================================
+ Hits 34624 34719 +95
+ Misses 1463 1451 -12 ☔ View full report in Codecov by Sentry. |
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.
LGTM
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Fixes issue mapping environment to engine environment post v2 versioning merge.
Note that another option here would be to change the mapping function to use e.g. the
versioning_service.get_environment_feature_states
function, but this would result in database query issues.How did you test this code?
Added a specific unit test to replicate the issue seen in production.