…mplates

# Conflicts:
#	data/saas/dataset/mailchimp_dataset.yml
#	src/fidesops/main.py
#	src/fidesops/ops/api/v1/endpoints/saas_config_endpoints.py

…key already exists.

…te in the template endpoint. Don't save ConnectionConfig until secrets are validated.

…s and datasets with instance_fides_key.

- Fix datadog yaml so it can be included in the saas connector registry. There was an error in how the saas config was formatted.

…to have brackets around the "instance_fides_key" to indicate these will be replaced.

Update the fides_key definition to allow "<instance_fides_key>" with brackets specifically to pass validation.

…crets that should be supplied for a given connector. Use the saas config type instead of the fides key for the model title. Add test verifying that fides key /instance key validation works as expected.

…mplates

- Add new endpoint to postman collection
- Add drafts doc.
- Update old response body in docs for connection types.

…in the saas fixtures.

…onConfig.

…es_key.

…ser-* data categories after the fideslang update, so they would show up if the user picked a "user" data category.

…mplates

# Conflicts:
#	CHANGELOG.md
#	docs/fidesops/docs/postman/Fidesops.postman_collection.json