Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add considerations for multi instance of destinations #6259

Merged
merged 3 commits into from
May 28, 2024

Conversation

courtneyga
Copy link
Contributor

Proposed changes

It'd be helpful to add the considerations when considering this feature

Merge timing

Related issues (optional)

@courtneyga courtneyga marked this pull request as ready for review April 7, 2024 02:15
@courtneyga courtneyga requested a review from a team as a code owner April 7, 2024 02:15
@courtneyga courtneyga requested review from forstisabella and removed request for a team April 7, 2024 02:15
@@ -101,6 +101,15 @@ For example, you might set up a single Segment source to send data both to separ

You can also connect multiple instances of a destination to help you smoothly migrate from one configuration to another. By sending each version the same data, you can check and validate the new configuration without interrupting use of the old one.

However, there are a few considerations:
Copy link
Contributor

@forstisabella forstisabella Apr 9, 2024

Choose a reason for hiding this comment

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

hi @courtneyga - these are all good points and would make a useful addition to the docs!

I do have a few questions, though:

  • How can a user tell if a destination can connect multiple instances to the same source? Is there an attribute in the partner portal that the docs team could use to build some autogenerated info on each destination's docs page, or a big list on this page?
  • What is a hybrid actions destination?
  • Does the restriction about Data Lakes hold true for AWS, Azure, and Databricks data lakes?

Thanks!

src/connections/destinations/add-destination.md Outdated Show resolved Hide resolved
src/connections/destinations/add-destination.md Outdated Show resolved Hide resolved
src/connections/destinations/add-destination.md Outdated Show resolved Hide resolved
src/connections/destinations/add-destination.md Outdated Show resolved Hide resolved
@forstisabella forstisabella merged commit 9ab5cc4 into develop May 28, 2024
2 of 3 checks passed
@forstisabella forstisabella deleted the courtneyga-patch-26 branch May 28, 2024 19:25
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants