Add encryption_configuration parameter to BigQueryCheckOperator and BigQueryTableCheckOperator #39432
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
boring-cyborg
bot
added
area:providers
provider:google
…igQueryTableCheckOperator
molcay
force-pushed
the
feat/add-cmek-key-param-to-bigquery
branch
from
0eee331
to
934f6b9
Compare
|
Hi @potiuk ! |
potiuk
approved these changes
May 9, 2024
66 tasks
pateash
pushed a commit
to pateash/airflow
that referenced
this pull request
May 13, 2024
…igQueryTableCheckOperator (apache#39432)
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
…igQueryTableCheckOperator (apache#39432)
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.
This PR contains adding
encryption_configurationparameter to theBigQueryCheckOperatorandBigQueryTableCheckOperatorto add CMEK key support for these operator.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.