docs: move standards into their own sub-section (#560)
This commit is contained in:
1 parent
09a214463f
commit
7eaf6d6d48
7 files changed
+31
-25
No files matched your search
+2
-2
@@ -6,7 +6,7 @@ description: |-
|
||||
Boundary's CLI standards
|
||||
---
|
||||
|
||||
# Overview
|
||||
# CLI Standards
|
||||
|
||||
Boundary's CLI has predictable behavior throughout its various commands. This page details these standards to help users make better use of the CLI.
|
||||
|
||||
@@ -77,4 +77,4 @@ Boundary's CLI supports autocompletion. For Bash, the following line in a `~/.ba
|
||||
|
||||
`complete -C /path/to/boundary boundary`
|
||||
|
||||
This will allow tab completion of commands, flags, and in some cases the parameters to those flags.
|
||||
This will allow tab completion of commands, flags, and in some cases the parameters to those flags.
|
||||
+4
-4
@@ -1,12 +1,12 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: API Standards
|
||||
sidebar_title: API Standards
|
||||
page_title: HTTP API Standards
|
||||
sidebar_title: HTTP API Standards
|
||||
description: |-
|
||||
Boundary's API standards
|
||||
Boundary's HTTP API standards
|
||||
---
|
||||
|
||||
# Overview
|
||||
# HTTP API Standards
|
||||
|
||||
Boundary's HTTP API adheres to a set of standards that are rigidly followed. At its core, it is a standards-compliant JSON API for both input and output.
|
||||
|
||||
+2
-2
@@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Concepts - Standards
|
||||
page_title: API Standards
|
||||
sidebar_title: API Standards
|
||||
description: |-
|
||||
An introduction to Boundary API standards.
|
||||
@@ -8,4 +8,4 @@ description: |-
|
||||
|
||||
# Boundary API Standards
|
||||
|
||||
This section covers our API standards including command line, and other API interactions.
|
||||
This section covers our API standards including command line and HTTP API.
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Architecture
|
||||
sidebar_title: Security Model
|
||||
description: |-
|
||||
Boundary security model
|
||||
---
|
||||
|
||||
# Overview
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Security Model
|
||||
sidebar_title: Security Model
|
||||
description: |-
|
||||
Boundary security model overview.
|
||||
---
|
||||
|
||||
# Security Model
|
||||
|
||||
This section describes the security models that Boundary follows. Here you can find in-depth analysis about how permissions, identity, and target security are handled within the Boundary product.
|
||||
+4
-4
@@ -1,12 +1,12 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Permissions
|
||||
sidebar_title: Permissions
|
||||
page_title: Permissions Model
|
||||
sidebar_title: Permissions Model
|
||||
description: |-
|
||||
Boundary's permissions model
|
||||
---
|
||||
|
||||
# Overview
|
||||
# Boundary Permissions Model
|
||||
|
||||
Boundary's permissions model is a composable, RBAC, allow-only model that
|
||||
attempts to marry flexibility with usability. This page discusses the permission
|
||||
@@ -1299,4 +1299,4 @@ wildcard or templated grant strings.
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<!-- END TABLE -->
|
||||
<!-- END TABLE -->
|
||||
@@ -29,7 +29,12 @@ export default [
|
||||
{
|
||||
category: 'concepts',
|
||||
content: [
|
||||
'security-model',
|
||||
{
|
||||
category: 'security-model',
|
||||
content: [
|
||||
'permissions-model',
|
||||
]
|
||||
},
|
||||
{
|
||||
category: 'domain-model',
|
||||
content: [
|
||||
@@ -52,13 +57,12 @@ export default [
|
||||
],
|
||||
},
|
||||
{
|
||||
category: 'standards',
|
||||
category: 'api-standards',
|
||||
content: [
|
||||
'api-standards',
|
||||
'http-standards',
|
||||
'cli-standards',
|
||||
]
|
||||
},
|
||||
'permissions',
|
||||
],
|
||||
},
|
||||
'---',
|
||||
|
||||
Reference in new issue
Block a user