Backport of docs: Add enterprise badge into release/0.14.x #3998
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-secure-boundary
requested a review
from a team
as a code owner
hc-github-team-secure-boundary
requested review from
sarahethompson and
claire-labry
and removed request for
a team
hc-github-team-secure-boundary
force-pushed
the
backport/dheath-ent-nav-badge/marginally-national-squid
branch
from
3c4a468 to
deec8b1
Compare
hc-github-team-secure-boundary
deleted the
backport/dheath-ent-nav-badge/marginally-national-squid
branch
|
Database schema diff between To understand how these diffs are generated and some limitations see the FunctionsUnchanged TablesUnchanged ViewsUnchanged TriggersUnchanged IndexesUnchanged ConstraintsUnchanged Foreign Key ConstraintsUnchanged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #3981 to be assessed for backporting due to the inclusion of the label backport/website.
The below text is copied from the body of the original PR.
This pull request adds enterprise badges/alerts to Boundary docs pages where it is appropriate to call out that a feature is supported only in Enterprise or HCP Boundary. The enterprise badge and enterprise alert are existing devdot web components.
I added an HCP/ENT badge to the table of contents for any topics that only apply to one of the Enterprise versions. If there are nested topics, I only applied the badge to the top level:
For other examples in the TOC, view:
At the topic level, I added an alert to any topics or sections that only applied to one of the Enterprise versions. I added the alert directly under the level 1 heading, if the whole topic was targeted to the Ent versions:
I can't change the Boundary logo in the alert, but I did add the text "This feature requires HCP Boundary or Boundary Enterprise" and included a link to the product page (similar to Vault).
If only one section of a topic applies to the Enterprise versions, I added the alert directly underneath the relevant heading. See the example here for Credential injection in the Credential management topic:
I did a find/replace for any places where we were still using the HCP/ENT "sup" tag and replaced them with the alert. There are a couple exceptions where I left an inline "sup" tag, if we used it in a sentence in a field definition. It seemed disruptive to include the alert in the middle of a paragraph. But there aren't many instances like that.
This is a manual process, so we would have to remember to add the tag/alert for new features going forward.
See the changes in the preview deployment