-
Notifications
You must be signed in to change notification settings - Fork 554
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
Enable Snowflake as a Database Resource #983
Conversation
I can remove the dependency updates, but I ran suggested vendor commands (and those were updated). |
@bjsemrad - can you get this rebased with master? |
46a7584
to
78c6676
Compare
@robbruce rebased, and updated mods/tidy sorry it took a bit. |
Would love to use this. Is there any plan to get this merged? Was just going to put this together basically the same and then found this one. Happy to look into the Conflicts if @bjsemrad is unable to at this point. |
@chriskuchin I’ll rebase this again tonight. Sorry not actively watching it. |
No worries thanks appreciate that. @robbruce once that is fixed is there anything else that is needed to get this merged? |
@chriskuchin - I’m not a code maintainer, just a consumer. Thanks for keeping it up to date though! |
ahh ok I will see if i can chase down looking at git history a maintainer after the conflicts are cleaned up and see if we can get this merged |
@tvoran you seem to be the only active maintainer on this repo. Once the conflicts are cleaned up do you need anything else to get this added to the provider? Happy to write up an issue or anything else you need to get this pulled into the provider. Thanks |
78c6676
to
e4e79d8
Compare
@chriskuchin PR was updated I'll try to watch this more closely. |
"account": { | ||
Type: schema.TypeString, | ||
Required: true, | ||
Description: "The Account Name for the snowflake connection. Formats <accountname> if in us-west-2, or <accountname>.<region> for any other region", | ||
}, |
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 curious why this schema breaks the connection_url
API parameter up into its components? Is it just for convenience?
What do you think about just following the API parameters, and including good examples in the docs for different types of connection_url's? It also looks like in order to support root credential rotation, we need to be able to specify the connection_url
separately from the username
and password
.
Also this schema seems to be missing the max_open_connections
, max_idle_connections
, max_connection_lifetime
, and username_template
parameters.
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 agree that just a connection_url makes sense.
The host name can be more than just account
.region
, depending if Snowflake organisations and/or PrivateLink is being used.
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.
Yea I was trying to simplify the configuration / allow parameterization for terraform to abstract away what might change. Thinking about it more just simplifying it will make this require less changes in the future. Will update tonight.
Not sure how I missed the max connections etc, might have just not committed it originally.
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.
@tvoran please check the latest, this should cover it and use the additional api items added after the original PR.
@bjsemrad sorry to be that guy... But if you don't have time i can fork off of your changes and address the comments above |
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
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.
@bjsemrad this is awesome thanks so much for handling all this
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
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.
Almost there! Just one suggestion in the test, and there are a couple spacing issues that make fmt
will fix.
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
Co-authored-by: Theron Voran <tvoran@users.noreply.github.com>
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!
Thanks really appreciate all the work here!!! |
Community Note
Output from acceptance testing: