Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

Braze Connector: Access Endpoints #1248

Merged
merged 5 commits into from
Sep 29, 2022
Merged

Braze Connector: Access Endpoints #1248

merged 5 commits into from
Sep 29, 2022

Conversation

sadaqatullah
Copy link
Contributor

@sadaqatullah sadaqatullah commented Sep 2, 2022

Purpose

Implements Braze PII endpoints.

Checklist

  • Update CHANGELOG.md file
    • Merge in main so the most recent CHANGELOG.md file is being appended to
    • Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
    • Add a link to this PR at the end of the description with the PR number as the text. example: #1
  • Good unit test/integration test coverage
  • The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket

Fixes #322

@sadaqatullah sadaqatullah linked an issue Sep 2, 2022 that may be closed by this pull request
@sadaqatullah sadaqatullah changed the title Braze Connector [Draft] Braze Connector: Access Endpoints Sep 26, 2022
@galvana galvana closed this Sep 27, 2022
* Added Erasure Endpoints.

* Test Cases

* Finalized yml Files

* Finalized tests and fixtures

* Black Fix
CHANGELOG.md Outdated
@@ -78,6 +78,7 @@ The types of changes are:
* Frontend - Configure a Manual entry connector [#1015](https://github.com/ethyca/fidesops/pull/1247)
* Manual webhook test functionality [#1323](https://github.com/ethyca/fidesops/pull/1323/)
* Added change request table [#1340](https://github.com/ethyca/fidesops/pull/1340)
* Adds Access Endpoints for Braze [#1248](https://github.com/ethyca/fidesops/pull/1248)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to Access and erasure support for Braze and moved it to the Unreleased section.

test_request:
method: GET
path: /email/hard_bounces/
headers:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test request will use the same auth as the client_config so there is no need to specify the headers here. Also, you can just use the <api_key> placeholder here without having to use a param_value (I know this last one is a bit weird).

- fides_key: <instance_fides_key>
name: Braze Dataset
description: A sample dataset representing the Braze connector for Fidesops
collections:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work tagging the fields with the appropriate data categories 👍

@galvana galvana added the run unsafe ci checks Triggers running of unsafe CI checks label Sep 28, 2022
@galvana galvana added run unsafe ci checks Triggers running of unsafe CI checks and removed run unsafe ci checks Triggers running of unsafe CI checks labels Sep 28, 2022
@galvana galvana added run unsafe ci checks Triggers running of unsafe CI checks and removed run unsafe ci checks Triggers running of unsafe CI checks labels Sep 28, 2022
@galvana galvana merged commit e4a5816 into main Sep 29, 2022
@galvana galvana deleted the 322-braze branch September 29, 2022 04:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
run unsafe ci checks Triggers running of unsafe CI checks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Braze
2 participants