This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Starting point for SaaS connector templates * Fix imports from restructuring. * Get happy path working for instantiate connector from template endpoint. * Remove updating connector instances for now - out of scope. * Test nonexistent templates, secrets validation, instance key / fides key already exists. * Create DatasetConfigs and ConnectionConfigs instead of create_or_update in the template endpoint. Don't save ConnectionConfig until secrets are validated. * Add the other saas connectors to the registry and update their configs 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. * Update the fides_keys in the existing saas configs and dataset yamls 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. * Fix a side effect on a separate endpoint that returns the types of secrets 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. * - Update CHANGELOG - Add new endpoint to postman collection - Add drafts doc. - Update old response body in docs for connection types. * Replace the <instance_fides_key> with a properly formatted fides_key in the saas fixtures. * If DatasetConfig creation fails, delete the recently created ConnectionConfig. * Address some of the saas integration tests where I've changed the fides_key. * Fix typos. * Fix typo. * Fix unrelated bug where hubspot dataset has new datacategories with user-* data categories after the fideslang update, so they would show up if the user picked a "user" data category. * Respond to CR. Co-authored-by: Dawn Pattison <[email protected]>
- Loading branch information
Showing
75 changed files
with
1,319 additions
and
244 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,59 +1,59 @@ | ||
saas_config: | ||
- fides_key: datadog_connector_example | ||
name: Datadog SaaS Config | ||
type: datadog | ||
description: A sample schema representing the Datadog connector for Fidesops | ||
version: 0.0.1 | ||
fides_key: <instance_fides_key> | ||
name: Datadog SaaS Config | ||
type: datadog | ||
description: A sample schema representing the Datadog connector for Fidesops | ||
version: 0.0.1 | ||
|
||
connector_params: | ||
- name: domain | ||
- name: api_key | ||
- name: app_key | ||
- name: page_size | ||
connector_params: | ||
- name: domain | ||
- name: api_key | ||
- name: app_key | ||
- name: page_size | ||
|
||
client_config: | ||
protocol: https | ||
host: <domain> | ||
client_config: | ||
protocol: https | ||
host: <domain> | ||
|
||
test_request: | ||
method: GET | ||
path: /api/v2/logs/events | ||
headers: | ||
- name: DD-APPLICATION-KEY | ||
value: <app_key> | ||
- name: DD-API-KEY | ||
value: <api_key> | ||
test_request: | ||
method: GET | ||
path: /api/v2/logs/events | ||
headers: | ||
- name: DD-APPLICATION-KEY | ||
value: <app_key> | ||
- name: DD-API-KEY | ||
value: <api_key> | ||
|
||
endpoints: | ||
- name: events | ||
requests: | ||
read: | ||
method: GET | ||
path: /api/v2/logs/events | ||
headers: | ||
- name: DD-APPLICATION-KEY | ||
value: <app_key> | ||
- name: DD-API-KEY | ||
value: <api_key> | ||
query_params: | ||
- name: filter[query] | ||
value: <email> | ||
- name: filter[from] | ||
value: 0 | ||
- name: filter[to] | ||
value: now | ||
- name: page[limit] | ||
value: <page_size> | ||
param_values: | ||
- name: app_key | ||
connector_param: app_key | ||
- name: api_key | ||
connector_param: api_key | ||
- name: email | ||
identity: email | ||
data_path: data | ||
pagination: | ||
strategy: link | ||
configuration: | ||
source: body | ||
path: links.next | ||
endpoints: | ||
- name: events | ||
requests: | ||
read: | ||
method: GET | ||
path: /api/v2/logs/events | ||
headers: | ||
- name: DD-APPLICATION-KEY | ||
value: <app_key> | ||
- name: DD-API-KEY | ||
value: <api_key> | ||
query_params: | ||
- name: filter[query] | ||
value: <email> | ||
- name: filter[from] | ||
value: 0 | ||
- name: filter[to] | ||
value: now | ||
- name: page[limit] | ||
value: <page_size> | ||
param_values: | ||
- name: app_key | ||
connector_param: app_key | ||
- name: api_key | ||
connector_param: api_key | ||
- name: email | ||
identity: email | ||
data_path: data | ||
pagination: | ||
strategy: link | ||
configuration: | ||
source: body | ||
path: links.next |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.