Make function API access rights non nullable π ποΈ#8022
Make function API access rights non nullable π ποΈ#8022mergify[bot] merged 7 commits intoITISFoundation:masterfrom
Conversation
|
@matusdrobuliak66 Maybe check carefully if the migration script might not cause problem. (I don't think so). And I guess during deployment, if some of these fields are null (which they shouldn't), it could cause a migration issue. |
Codecov ReportAll modified and coverable lines are covered by tests β
Additional details and impacted files@@ Coverage Diff @@
## master #8022 +/- ##
==========================================
+ Coverage 87.88% 90.01% +2.12%
==========================================
Files 1853 1542 -311
Lines 71478 60931 -10547
Branches 1258 547 -711
==========================================
- Hits 62820 54847 -7973
+ Misses 8294 5940 -2354
+ Partials 364 144 -220
Continue to review full report in Codecov by Sentry.
π New features to boost your workflow:
|
|
@mergify queue |
β The pull request has been merged automaticallyDetailsThe pull request has been merged automatically at 7d6abf5 |
|
@mergify update |
βοΈ Nothing to do, the required conditions are not metDetails
|
...mcore_postgres_database/migration/versions/d159ac30983c_make_func_api_access_non_nullable.py
Show resolved
Hide resolved
...mcore_postgres_database/migration/versions/d159ac30983c_make_func_api_access_non_nullable.py
Show resolved
Hide resolved
|
|
@mergify refresh |
β Pull request refreshed |



What do these changes do?
As reported by @matusdrobuliak66, function API access rights were nullable, which should not be the case.
Related issue/s
Fixes #7966
How to test
Try to set function api access right to null.
Dev-ops