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

Support go-sockaddr templates in top-level cluster_addr config #13678

Merged
merged 2 commits into from Jan 19, 2022

Conversation

ncabatoff
Copy link
Collaborator

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting. As such, go-sockaddr templating needs to be implemented for the top-level cluster_addr setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.

…lly used, or at least isn't as important as the top-level clusteraddr setting. As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
@ncabatoff ncabatoff added this to the 1.9.3 milestone Jan 17, 2022
@ncabatoff ncabatoff requested a review from a team January 17, 2022 14:22
@vercel vercel bot temporarily deployed to Preview – vault January 17, 2022 14:33 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 17, 2022 14:33 Inactive
@ncabatoff ncabatoff added backport/1.9.x backport/website-deprecated Backport changes to `stable-website` and the latest `release/#.#.x` branch and removed backport/website-deprecated Backport changes to `stable-website` and the latest `release/#.#.x` branch labels Jan 19, 2022
@ncabatoff ncabatoff merged commit 4970b33 into main Jan 19, 2022
@ncabatoff ncabatoff deleted the sockaddr-template-clusteraddr branch January 19, 2022 15:56
ncabatoff added a commit that referenced this pull request Jan 19, 2022
In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
ncabatoff added a commit that referenced this pull request Jan 20, 2022
… (#13706)

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
akshya96 pushed a commit that referenced this pull request Jan 20, 2022
… (#13706)

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
joatmon08 pushed a commit that referenced this pull request Jan 25, 2022
In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
qk4l pushed a commit to qk4l/vault that referenced this pull request Feb 4, 2022
…corp#13678)

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants