-
Notifications
You must be signed in to change notification settings - Fork 72
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
Unnest ops
API code
#3318
Unnest ops
API code
#3318
Conversation
Passing run #2055 ↗︎
Details:
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #3318 +/- ##
=======================================
Coverage 87.07% 87.07%
=======================================
Files 313 313
Lines 18968 18968
Branches 2473 2473
=======================================
Hits 16517 16517
Misses 2009 2009
Partials 442 442
☔ 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.
this looks good, did some smoke testing on my local server too and things generally looked fine.
only question is around the failures with external saas tests - i'm almost positive those are unrelated to the changes, just the fact that there are so many (and with some rather unusual suspects from my experience) gives me pause. there also aren't any logs showing the failures/errors - maybe this is normal in CI?
looping in @galvana who's got some more recent experience with the saas tests to make sure things look OK from his POV!
That is correct, we don't show those test logs in CI for security reasons. To put it simply, I did a mass search find for any mention of To avoid continually spending time on merge conflicts, I'd rather ship now and follow up with a smaller PR that might fix any particular bug that slipped through |
that's good with me! sorry, looks like you've already got some conflicts :/ |
haha no worries! I knew I wouldn't get away clean this time 😂 after going through the Fides 2.0 merge I think I can handle just about anything in terms of conflicts |
Code Changes
fides.api.ops
dir up one intofides.api
Steps to Confirm
Pre-Merge Checklist
CHANGELOG.md
Description Of Changes
In preparation for fully integrating ops/ctl code, this small (but with a large diff 😬 ) iteration unnests the ops code into
fides.api