Added code to handle authenticator issue posted in issue #85
Added snowflake library installation to avoid initialization failures for brickflow plugins
enhanced the code to accept parameters based on load_type instead of making every parameter mandatory.
Related Issue
fix #85
Motivation and Context
At this point code is failing for user id's which require extra authentication mechanism which is blocking multiple brickflow consumers. As we added snowflake operator to initialize with brickflow_plugins it is looking for snowflake library and causing issues to some customers, fixing this issue. Current version of the operator expects optional parameters like sf_cluster_keys, incremental_filter, sf_grantee_roles even when they are not required for customers and causing issues.
How Has This Been Tested?
Created a wheel file , workflow and tested with user id that require and doesn't require extra authentication. ran multiple test cases with different combination of input params. created a notebook with operator code and ran multiple manual unit tests.
Screenshots (if appropriate):
Types of changes
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
Description
Added code to handle authenticator issue posted in issue #85 Added snowflake library installation to avoid initialization failures for brickflow plugins enhanced the code to accept parameters based on load_type instead of making every parameter mandatory.
Related Issue
fix #85
Motivation and Context
At this point code is failing for user id's which require extra authentication mechanism which is blocking multiple brickflow consumers. As we added snowflake operator to initialize with brickflow_plugins it is looking for snowflake library and causing issues to some customers, fixing this issue. Current version of the operator expects optional parameters like sf_cluster_keys, incremental_filter, sf_grantee_roles even when they are not required for customers and causing issues.
How Has This Been Tested?
Created a wheel file , workflow and tested with user id that require and doesn't require extra authentication. ran multiple test cases with different combination of input params. created a notebook with operator code and ran multiple manual unit tests.
Screenshots (if appropriate):
Types of changes
Checklist: