-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Cc 7146/convert consul hcp to a simpler component for some upcoming changes #20344
Cc 7146/convert consul hcp to a simpler component for some upcoming changes #20344
Conversation
…onent-for-some-upcoming-changes
@hut just taking a look now. Is there a reason this is backported to 1.17 and not just applied to the new 1.18 release? I haven't followed past PRs so apologies if this works was always planned to be backported to 1.17.x |
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.
LGTM, question regarding license and backporting aside.
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 think you may want to also remove this bit?
consul/ui/packages/consul-ui/lib/startup/templates/body.html.js
Lines 111 to 114 in f42152a
'CONSUL_HCP_ENABLE': { | |
name: 'consul-hcp', | |
default: ${config.operatorConfig.HCPEnabled} | |
} |
Honestly, confusing. It looks like a IIFE that is called with an object of the features/packages that should be checked if they need to be included but we are also manually doing that above? I'm thinking it may be something that runs for either configuration enabled or if they are enabled by env vars? Not sure right now.
…rt-consul-hcp-to-a-simpler-component-for-some-upcoming-changes
…onent-for-some-upcoming-changes
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
2 similar comments
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
4 similar comments
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
8 similar comments
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
@chris-hut, a backport is missing for this PR [20344] for versions [1.17] please perform the backport manually and add the following snippet to your backport PR description:
|
Description
As part of CC-7146 we'll be adding a sidebar item about the cluster's link status and need to modify the logic from the existing
Back to Consul
Nav bar item.This PR refactors the component that renders the
Back to consul
item in the following ways:consul-ui
package, for easier use and editingconsul-hcp
package to clean up a little bitTesting & Reproduction steps
yarn start
Scenario('CONSUL_HCP_ENABLE=1');
andScenario('CONSUL_HCP_URL=https://corn.com')
<- Back to HCP
nav bar itemLinks
PR Checklist
References