Thomas
Thomas
this is still a good idea, but in the meantime we've decided to package/document other good defaulty policies
@LKCSmith yep! We're waiting to get the user management (fideslib) code integrated before we can ship users-related things
correct, still waiting on the fideslib user management but its coming soon ™️
@allisonking I actually think #2 will work just fine! This is the chain of events that happens when the server starts up: 1. calls `configure_db` 2. calls `init_db` 3. runs...
@mfbrown I think this is worth getting on the board in sprint 5? to at least lay the pattern down, I foresee us needing to leverage it more and more...
@allisonking good news, the test is passing again! bad news....the merge conflicts 🙃
@allisonking do we need a follow-up issue for the tooltips TODO?
The original thinking around this was that system exits such as https://github.com/ethyca/fides/blob/f780ee8529648525f1d5d3c943e6ff4aa950cdae/src/fidesctl/cli/utils.py#L30 feel really weird. But also, I'm not sure how useful a custom exit or exception would be in...
@PSalant726 can you give some concrete examples so we can pattern match and figure out where to start implementing?
de-prioritizing this as it isn't critical for the 1.7 release