feat!: Add warm_up method to SnowflakeTableRetriever to delegate auth and database connection testing
#2414
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.
Related Issues
SnowflakeTableRetrieverProposed Changes:
authenticatorwhich matches the previous default behavior. We also set defaults for all Secrets instead of setting them to None by default.warm_upmethod ofSnowflakeTableRetriever. This allows for the component to be initialized without needing all secrets present. This is useful if you want to perform Pipeline validation without needing all secrets present.warm_upon the component before it can be used. This is only relevant if you are using this component in isolation. If being used in a Pipeline then the Pipeline will automatically call warm_up on it so usage of this component does not change.How did you test it?
Notes for the reviewer
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:.