Secret values are not properly filtered out in RedshiftSQLOperator
See original GitHub issueDuring the execution of extractor for RedshiftSQLOperator, in the URI for the datasource, attributes like access_key_id
and secret_access_key
have sensitive values exposed without getting obfuscated. These sensitive information should be shielded and not be visible when being emitted to OpenLineage.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
RedshiftSQLOperator — apache-airflow-providers-amazon ...
This is a basic example dag for using RedshiftSQLOperator to execute statements against an Amazon Redshift cluster. Create a table¶. In the following...
Read more >apache-airflow-providers-amazon - Python package - Snyk
Based on project statistics from the GitHub repository for the PyPI package ... Avoid requirement that AWS Secret Manager JSON values be urlencoded....
Read more >Creating a secret and an IAM role to use federated queries
Choose Store a new secret. Choose the Credentials for RDS database tile. For User name and Password, enter values for your instance. Confirm...
Read more >What's new on the cloud for data engineers - part 5 (09-12.2021)
Subscribers can now query 3rd party data sets directly from Redshift without the need of copying the data to the clust.
Read more >AWS Secrets Manager in Use for Redshift Clusters - Trend Micro
If there is no secret key-value pair defined to store a Redshift database ... 08 Change the AWS region from the navigation bar...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Reopening to implement filtering per operator.
Hi Maciej,I think that makes much sense.extractors for specific operators should def. Know those!HowardSent from my iPhoneOn Oct 10, 2022, at 4:24 AM, Maciej Obuchowski @.***> wrote: @howardyoo I was thinking about operator/extractor specific ones. Generally I think we know which ones are relevant for given operator, like host, project name. This might be more relevant for operators that are responsible for it’s own lineage.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>