-
Notifications
You must be signed in to change notification settings - Fork 60
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
Pass region
param on to redshift conn as is
#485
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-redshift contributing guide. |
region
in the hostname
region
in the hostnameregion
param on to redshift conn as is
Loving how this is looking @colin-rogers-dbt 🤩 Since we're removing the region logic entirely in 2dfa187, we'll need to open an issue to update docs for this page: Specifically, to make this change in a couple different places: - region: # optional, if not provided, will be determined from host (e.g. host.123.us-east-1.redshift-serverless.amazonaws.com)
+ region: # optional |
As a follow-up to #485 (comment), opened up a PR to update the docs here: |
👋 Hi. A few questions:
|
This change is specifically for customers (like those using the Cloud IDE) who cannot pass the region parameter at this time.
For now you will not provide this parameter.
The region parameter is only required if using IAM auth so for Cloud IDE users this poses no risk. This change has been made after discussion with the maintainers of redshift-connector (where they are also doing this fallback inference in some places) with the decision that we don't want to maintain logic that should be handled by that package. |
Previews: - [Password-based authentication](https://deploy-preview-3519--docs-getdbt-com.netlify.app/docs/core/connect-data-platform/redshift-setup#password-based-authentication) - [IAM Authentication](https://deploy-preview-3519--docs-getdbt-com.netlify.app/docs/core/connect-data-platform/redshift-setup#iam-authentication) ## What are you changing in this pull request and why? dbt-labs/dbt-redshift#485 is updating handling of the `region` parameter for dbt-redshift to be completely optional without additional side-effects (like attempting to parse it from the host name). ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines.
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.
Late approval :p
* convert test_store_test_failures to functional test * test not requiring a region in hostname * remove dev-requirements.txt change * add unit test and clean up logic * add changie * simplify region inference logic * remove region logic entirely (cherry picked from commit cbb45ca)
* convert test_store_test_failures to functional test * test not requiring a region in hostname * remove dev-requirements.txt change * add unit test and clean up logic * add changie * simplify region inference logic * remove region logic entirely (cherry picked from commit cbb45ca) Co-authored-by: colin-rogers-dbt <[email protected]>
* convert test_store_test_failures to functional test * test not requiring a region in hostname * remove dev-requirements.txt change * add unit test and clean up logic * add changie * simplify region inference logic * remove region logic entirely
resolves #484 resolves #483
Description
Region is a non-obvious semi-requirement post 1.5 (you don't need to specify it if it's in your hostname), this has been a headache for various users and it's not clear that it's strictly speaking necessary.
This change makes it a truly optional requirement for dbt-redshift, this removes duplication with the underlying redshift-connector to properly manage and validate this parameter.
Checklist
changie new
to create a changelog entry