#11341 airbyte 1.4 docs #51576
Open
#11341 airbyte 1.4 docs #51576
+86
−49
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
… Updated the enterprise deployment guide to move custom images out of "Configure your Deployment" and into "Customizing Your Deployment", per Alex' suggestion.
…out with release. More needed later
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
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.
What
This is a rough/quick docs update to reflect changes in version 1.4. It's not fully comprehensive, but it does provide some insight into the fact that these things exist. We'll do another round later in the week to fill some of this out more.
How
I've added new information about private registry support for connector images.
Review guide
The main change is private registry support for connector images. It's the only change in this version requiring any substantial docs.
User Impact
Can this PR be safely reverted and rolled back?