-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
fix: apply db_port to actual instance #162
Conversation
/test all |
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.
It's amazing to me that we haven't caught this until now... Guess that goes to show how many folks just use the default port in 99% of cases.
Thanks for the quick fix @ekristen!
Looks like we had some errors on terratest, odd that it says that encryption is always enabled on Serverless. I'm actually using Serverless v2 right now that that's not the case, you can have un-encrypted clusters. |
@ekristen I'm sorry about this, it's a PITA, but can you do me a favor and add I'm not sure why this is failing now... but let's see if we can appease it and get this very reasonable and important fix in. Appreciate it! |
Head branch was pushed to by a user without write access
all good @Gowiem commit sent, lets see if we get tests to pass. |
/test all |
closing |
Not sure why this was closed, I created a new PR here #222 |
what
Makes the db_port effective. Currently it only modifies the security group, not the actual RDS port.
why
The current variable is broken, it modifies the security group but not the underlying cluster, therefore it's actually renders the variable ineffective as is. In fact if you do not set it do the default for the database type, the use of the module will not work.
references