copy seed files from airbyte-config/init/build to airbyte-server to be used in migrations #4428
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.
closes #4412
What
airbyte-server
to have access to the generated seed configs to make auto migration work. Instead of having those files live inairbyte-server
we continue to generate them inairbyte-config:init
but then copy them over toairbyte-server
How
While doing this I discovered this bug: https://github.com/airbytehq/airbyte-internal-issues/issues/156. Going to suggest we follow up on it separately and focus on just getting this deduplication of configs fixed. I think the fallout from this bug will generally be low.
This change is