feat(publish): Fail hard when Docker image doesn't exist instead of building #60899
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.
Remove Docker image build from publish operations
Description
This PR modifies the connector publish pipeline to fail hard when a Docker image does not exist, instead of automatically building and pushing the image. The desired behavior is to expect the image is already published and fail if not.
Changes
CheckConnectorImageDoesNotExistto return FAILURE status when an image doesn't existMotivation
This change allows for incremental migration away from using
airbyte-cifor publishing. By removing the automatic image building and requiring pre-published images, we create a cleaner separation of concerns between building and publishing operations.Testing
The changes have been tested by verifying:
Link to Devin run
https://app.devin.ai/sessions/7267998ffd284b52bfb21918e6694d41
Requested by
Aaron ("AJ") Steers (aj@airbyte.io)