add connected source docs #7258
Merged
Conversation
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
colleenkerr
requested review from
andrewcarlberg,
wendy-p,
josh-mccrowell-braze and
julianw-braze
_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md
Outdated
Show resolved
Hide resolved
|
|
||
| -- grant access to specific tables or views in the schema | ||
| GRANT SELECT ON TABLE BRAZE_CLOUD_PRODUCTION.INGESTION.USERS_ATTRIBUTES_SYNC TO ROLE BRAZE_INGESTION_ROLE; | ||
| ``` |
There was a problem hiding this comment.
We need the ability to create tables as well.
There was a problem hiding this comment.
Pushed a change to add this. Let me know if it looks ok!
_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md
Outdated
Show resolved
Hide resolved
_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md
Outdated
Show resolved
Hide resolved
|
|
||
| Cloud Data Ingestion connected sources require some setup on the Braze side and in your instance. | ||
|
|
||
| A connected source may reference one or more tables, so the user created for Braze to use should have permissions for all tables you want to be available in the connected source. Follow these steps to set up the integration: |
There was a problem hiding this comment.
I'm a little confused how these numbered steps relate, if at all, to the steps below. Are they supposed to be a separate prerequisite that you need to accomplish before you can begin setting up connected sources? Or are these a different way to number the steps below?
There was a problem hiding this comment.
I pushed a commit to try and clarify. The goal of this is just to show a brief summary of what the setup process will require. Can remove if you think that's better!
josh-mccrowell-braze
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request/Issue Resolution
Description of Change:
Closes #ISSUE_NUMBER_HERE
Is this change associated with a Braze feature/product release?
✔️ Pull Request Checklist
assets>js>broken_redirect_list.js⭐ Helpful Wiki Shortcuts
❗ ATTN: For PR Reviewers
❗ ATTN: Internal Reviewing Chart
Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @internetisaiah for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.
Quality Infrastructure
Platform Infrastructure
Datalake
SDKs
Currents
Technology partners
Channels
In-App Messages
Channels
Frontend Infrastructure & Experience (FIX)
Core Objects
Core Messaging
Messaging Experience
Message Components
Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
SMS
User Targeting
Reporting