-
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
docs: re-organize service and node lookups for Consul Enterprise #14389
Conversation
Co-authored-by: trujillo-adam <[email protected]>
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.
minor suggestion - pre-approving
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.
@david-yu : thanks for taking this on! I made some suggestions that:
- Make defaults explicit
- Break out virtual IP lookups from other service lookups
Co-authored-by: Jared Kirschner <[email protected]>
Co-authored-by: Jared Kirschner <[email protected]>
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.
@david-yu : small follow up after looking at the Vercel preview
Co-authored-by: Jared Kirschner <[email protected]>
Co-authored-by: Jared Kirschner <[email protected]>
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 - thanks David!
Description
Refactor enterprise node and service lookups into their respective sections, as opposed to having enterprise lookups in its own section.
Testing & Reproduction steps
Links
Include any links here that might be helpful for people reviewing your PR (Tickets, GH issues, API docs, external benchmarks, tools docs, etc). If there are none, feel free to delete this section.
Please be mindful not to leak any customer or confidential information. HashiCorp employees may want to use our internal URL shortener to obfuscate links.
PR Checklist