consul/local at 67254a924485bec90071016666cf41e92bbffed0 - consul - https://git.xinac.net

Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.

consul api-gateway kubernetes ecs service-discovery service-mesh vault

Tree: 67254a9244

History

hc-github-team-consul-core 6ed2c23572 Backport of Displays Consul version of each nodes in UI nodes section into release/1.16.x (#18113 ) ## Backport This PR is auto-generated from #17754 to be assessed for backporting due to the inclusion of the label backport/1.16. 🚨 >Warning automatic cherry-pick of commits failed. If the first commit failed, you will see a blank no-op commit below. If at least one commit succeeded, you will see the cherry-picked commits up to, _not including_, the commit where the merge conflict occurred. The person who merged in the original PR is: @WenInCode This person should manually cherry-pick the original PR into a new backport PR, and close this one when the manual backport PR is merged in. > merge conflict error: unable to process merge commit: "1c757b8a2c1160ad53421b7b8bd7f74b205c4b89", automatic backport requires rebase workflow The below text is copied from the body of the original PR. --- fixes #17097 Consul version of each nodes in UI nodes section @jkirschner-hashicorp @huikang @team @Maintainers Updated consul version in the request to register consul. Added this as Node MetaData. Fetching this new metadata in UI <img width="1512" alt="Screenshot 2023-06-15 at 4 21 33 PM" src="https://github.com/hashicorp/consul/assets/3139634/94f7cf6b-701f-4230-b9f7-d8c4342d0737"> Also made this backward compatible and tested. Backward compatible in this context means - If consul binary with above PR changes is deployed to one of node, and if UI is run from this node, then the version of not only current (upgraded) node is displayed in UI , but also of older nodes given that they are consul servers only. For older (non-server or client) nodes the version is not added in NodeMeta Data and hence the version will not be displayed for them. If a old node is consul server, the version will be displayed. As the endpoint - "v1/internal/ui/nodes?dc=dc1" was already returning version in service meta. This is made use of in current UI changes. <img width="1480" alt="Screenshot 2023-06-16 at 6 58 32 PM" src="https://github.com/hashicorp/consul/assets/3139634/257942f4-fbed-437d-a492-37849d2bec4c"> --- <details> <summary> Overview of commits </summary> - `931fdfc7ec` - `b3e2ec1cca` - `8d0e9a5490` - `04e5d88cca` - `28286a2e98` - `43e50ad382` - `0cf1b7077c` - `27f34ce1c2` - `2ac76d62b8` - `3d618df9ef` - `1c757b8a2c` - `23ce82b4ce` - `4dc1c9b4c5` - `85a12a9252` - `25d30a3fa9` - `7f1d6192dc` - `5174cbff84` </details> --------- Co-authored-by: Vijay Srinivas <vijayraghav22@gmail.com> Co-authored-by: John Murret <john.murret@hashicorp.com> Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>		1 year ago
..
state.go	continue anti-entropy sync when failures exist (#17560 )	1 year ago
state_internal_test.go	copyright headers for agent folder (#16704 )	2 years ago
state_test.go	Backport of Displays Consul version of each nodes in UI nodes section into release/1.16.x (#18113 )	1 year ago
testing.go	copyright headers for agent folder (#16704 )	2 years ago