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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for new DuckDB Secrets manager #403
Add support for new DuckDB Secrets manager #403
Changes from all commits
199a1b2
824ad79
d551db1
1672e38
51ed86f
84829e6
68394e8
1716959
c4dd7b8
670274f
ec92f03
5b2be62
a0abb89
34f4465
4928807
1a3ba12
5d9e063
9325fec
6be0283
9f681ab
d44e1d6
a0f706c
42df1dd
3dd50e7
0a1a2f6
93b4cf9
593683b
a8350a6
0d71fb6
9532524
cd0b9b2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering when we want to simply require >= 1.0.0? Is this materially different than that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also a little mentally fuzzy on how I should do minor/major version updates for adapters like dbt-duckdb since in theory we are now de-coupled from dbt-core versions via the dbt-adapters interface /cc @dbeatty10
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chiming in here from adapters, you are totally free to version as you see fit. We generally recommend that major version bumps reflect major changes to the adapter and should therefore be reserved. Minor versions should reflect meaningful changes to behavior.
Beyond versioning we do want to encourage adapters to keep it easy for folks to upgrade and to not surprise people with changes. To do that we want to introduce breaking behavioral changes as opt-in with a warning that the default behavior will change in a future version. We are going to be picking up a project in Q3 to add behavior flags to formalize this process. This should provide a framework for adapters to manage the life cycle of these changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks Colin, super-helpful context here 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to bump to 1.0.0 in a separate PR, I want to make sure there's a commit that still has 0.10.2 included in case someone turns up with that requirement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR open here!