Skip to content
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

Set custom per instance socket address #289

Merged
merged 8 commits into from Jun 25, 2019
Merged

Set custom per instance socket address #289

merged 8 commits into from Jun 25, 2019

Conversation

kurtisvg
Copy link
Contributor

Fork of #265, updated to include automatic addition of the suffix for Postgres instances.

wedi and others added 2 commits June 13, 2019 16:37
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@kurtisvg kurtisvg added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Jun 13, 2019
@kurtisvg kurtisvg requested a review from broady June 13, 2019 23:45
@kurtisvg kurtisvg requested a review from broady June 18, 2019 03:35
@wedi
Copy link

wedi commented Jun 24, 2019

Thanks for stepping in. Ofc I'm fine with that. 👍

@kurtisvg kurtisvg added cla: yes priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 24, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@kurtisvg kurtisvg merged commit fa714b4 into master Jun 25, 2019
@kurtisvg kurtisvg deleted the named-socket branch June 25, 2019 21:14
broady added a commit that referenced this pull request Aug 26, 2019
PR #289 broke this support by using net.JoinHostPort, which wraps a v6
address in square brackets, e.g. [::1]

This resulted in a double-wrapping - the resultant address was something
like "[[::1]]:3306".

Also add tests explicitly for listening on the "tcp4" and "tcp6" nets.
broady added a commit that referenced this pull request Aug 26, 2019
PR #289 broke this support by using net.JoinHostPort, which wraps a v6
address in square brackets, e.g. [::1]

This resulted in a double-wrapping - the resultant address was something
like "[[::1]]:3306".

Also add tests explicitly for listening on the "tcp4" and "tcp6" nets.
kurtisvg pushed a commit that referenced this pull request Aug 26, 2019
PR #289 broke this support by using net.JoinHostPort, which wraps a v6
address in square brackets, e.g. [::1]

This resulted in a double-wrapping - the resultant address was something
like "[[::1]]:3306".

Also add tests explicitly for listening on the "tcp4" and "tcp6" nets.
@kurtisvg kurtisvg mentioned this pull request Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants