Add a repository method that determines if a connection has an alpha or beta connector #22190
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
Airbyte Code Coverage
|
This was referenced Feb 8, 2023
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
In order to determine whether a particular connection should be allowed to continue running even in a delinquent workspace with negative credits, we need a simple way to check if a connection has an alpha or beta connector. This check should be performant so that we can perform it in API call validations and in our billing cron.
How
Write a new configRepository method that joins the connection with actor -> actor_definition and uses the definition's release stage to return a boolean.
Cloud will call this new method when validating free connector usage in the API and cron.