Guen Prawiroatmodjo
Guen Prawiroatmodjo
> @guenp wanted to clarify the issue with the glue plugin; one could still specify the necessary S3 info in the `settings`, right? But if you wanted to e.g. use...
> Ah so this wouldn't be backwards compatible, then-- folks would need to cut over to the new way. I'm assuming there's got to be a similar deprecation schedule for...
> `use_credential_provider` no longer uses boto3 to fetch the credentials from aws SSO. This is actually incorrect, I checked and `boto3` can fetch the creds from AWS SSO itself. So...
Oops! I didn't mean to add all those labels - I ran the formatter and accidentally pushed files unrelated to this PR. Could someone please remove them? 🙇♀️
Thanks @matsonj for reporting! This looks like it's not a bug in `dbt-duckdb`, but I am investigating and will follow up here once we figure it out.
Hi @matsonj , just to loop back with you on this - it looks like a patch for a [security vulnerability](https://github.com/duckdb/duckdb/security/advisories/GHSA-w2gf-jxc9-pf2q) caused this error. It will be fixed in DuckDB...
Thanks, @dataders for catching this!
Done! Thank you @matsonj for your help
@g-diwakar , do you still experience this error on the latest version of DuckDB?
@Dinesh-0813 yes you can!! Please let us help you though, if you can make a minimal repro we can help point you in the right direction