* Make helm unit tests use hard-coded version to avoid updating snapshots with each release.
* Remove helm unittests after version update
* Used v99 for tests
* Upgraded helm unittest plugin
* Implement guarenteed helm unittest version at runtime
* Use bash for helm-unittest install so we can have pipefail
* Fix unittest version check
* Fixed dup unittest plugins
* Fixed helm unittest version copy command in Dockerfile
* Fixed version test
* Consolidate Reference docs section contents
Closes#56206
Reduce the number of first-level children in the Reference section of
the docs from 23 to 9, not counting the index page available at
`/docs/reference/`. This makes the Reference section easier to navigate,
since a user can more readily form a mental model of the content
available in the section with fewer items and a more thematic
organization.
- Add a section for deployment references, consolidating reference
guides for configuring and architecting a Teleport deployment.
- Move the Predicate Language and User Types references into the Access
Controls section of References.
- Add a section for API reference guides, consolidating the Terraform,
MWI Terraform, and Operator sections.
- Move Cloud FAQ to Quick Links. This places the guide next to the main
FAQ in the sidebar to make it more discoverable, since the guide is
currently rather hidden. This also helps pave the way to merge the two
FAQs in the future.
* Add an MWI reference section
The MWI Terraform module reference does not belong with reference guides
for API clients. Add a section to the reference guide for Machine &
Workload Identity.
* Rename "API" to "Infrastructure as Code"
Teleport users expect tctl, Operator, and Terraform Provider docs to be
in an Infrastructure as Code reference section, rather than the more
vague "API" section.
Responds to **ravicious** feedback.
Move Identity Governance-related how-to guides into a dedicated
documentation sidebar section so readers are aware of this product as a
top-level offering. This is part of a broader initiative to add a
top-level documentation section for each Teleport product.
* build: Update master for v19
Update the version in `master` to v19 now that the v18 branch has been
cut. This will cause all dev builds to be built with v19.0.0-dev version
prefix and use a teleport19 buildbox. The buildbox has been manually
built prior to this commit being merged to master.
Run `make update-version` to propagate the new version to required
files.
Remove no-longer-necessary steps in the preflight.md docs.
* fix: allow tests to use old client versions
---------
Co-authored-by: Tim Ross <tim.ross@goteleport.com>
Provide a less overwhelming documentation experience for users by
condensing sidebar sections into five, organized loosely around
different audiences of the documentation:
- **Get Started:** new Teleport users, as well as users of all levels
who want to quickly look up key, frequently changing information, such
as the changelog and upcoming release information.
- **Admin Guides:** intermediate users completing a specific task. This
includes all how-to guides in the docs except those in "Get Started"
and "Enroll Resources".
- **Enroll Resources:** Admin Guides, but for our extensive library of
how-to guides for protecting infrastructure resources with Teleport.
- **References:** Advanced users looking for comprehensive reference
information and architecture guides. This includes all reference
guides in the docs.
- **User Guides:** Guides for end users looking to access resources.
Related changes:
- **Move Helm reference partials**. Use the `docs/pages/includes`
directory so we can generate the sidebar from `docs/pages/reference`.
- **Move the Architecture sidebar section** into "References", and move
architecture guides across the documentation into "Architecture".
- **Remove "Documentation Overview"** as this is out of date. Now, top-level
sidebar sections are more self explanatory.
- **Remove "Choose an Edition"**, since we want to elevate Teleport
Enterprise (Cloud), making Teleport Enterprise (Self-Hosted) available
for certain use cases.
- **Add an infrastructure as code section** to Admin Guides.
Adam Carheden