mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-12 02:15:01 +00:00
Paul Gottschling
cc89378c3d
We are standardizing docs guides to add a page_type frontmatter field, with values for how-to guides, references, etc. We can then use this field to apply linting rules that ensure each guide type follows type-specific docs site conventions. The first convention is that each docs page must have an outcome statement, the structure of which depends on the guide's type. Human and AI agent readers can determine from the outcome statement whether to continue reading the guide or not. This change assigns the `page_type` frontmatter field to 55 guides. Where an outcome statement is missing, it adds one. Where an outcome statement exists, it ensures that the statement matches the standard structure so we can add a linter later on. (A majority of guides were already compliant.)
16 lines
331 B
Plaintext
16 lines
331 B
Plaintext
---
|
|
title: Database Access Reference
|
|
sidebar_label: Reference
|
|
sidebar_position: 8
|
|
description: Configuration and CLI reference for the Teleport Database Service.
|
|
tags:
|
|
- zero-trust
|
|
- infrastructure-identity
|
|
page_type: landing
|
|
---
|
|
|
|
- [CLI](cli.mdx)
|
|
- [Audit Events](audit.mdx)
|
|
- [AWS IAM](aws.mdx)
|
|
- [Database Labels](labels.mdx)
|