Steve Murphy

After a quick chat in office hours today, it felt like some extra scope/detail could be added. Some initial questions that came out of it (feel free to add anything...

> The primary intent of this feature is to allow organizations to store credentials within the server, so that the server itself can run regular coverage checks without someone needs...

I liked the way Meltano did this as well 👍🏽 Being able to have a clear definition for how to set env vars and use them would also give us...

I think this would be a big enabler as part of the release process, can see this being handy with cutting a release 👍🏽 thanks for opening this up!

@brentonmallen1 feel free to add any other context or modify anything that maybe seems misaligned with what you were thinking

Thanks for the thoughts @ThomasLaPiana ! I think the idea of having it optional makes a lot of sense, challenges with datasets have become much more clear to me since...

I'm currently exploring a temporary workaround in #350 by altering the `upsert` method used, but will plan to try and get some conversations started around the merits of modifying how...

Great, thanks @ThomasLaPiana ! Yes, data uses are in the same boat, but in general the separate fides key should keep issues lower than the organization. I _think_ changing the...

Totally agree, based on what you mention there it feels like something `load_default_taxonomy` could be handled as part of the `fidesctl init` workflow instead of being somewhat implicit as part...

Need to see if the work from #421 by @PSalant726 means we can close this or if we still want to review making a change here