From 4509981e5bb57ad1b34a39fe78d642ba459c4e18 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Fri, 11 Nov 2022 15:57:07 -0500 Subject: [PATCH] Fix pull-down placement (#2610) --- website/content/docs/concepts/filtering/events.mdx | 6 ++---- .../docs/concepts/filtering/oidc-managed-groups.mdx | 8 ++++---- .../content/docs/concepts/filtering/resource-listing.mdx | 4 ++-- website/content/docs/concepts/filtering/worker-tags.mdx | 4 ++-- 4 files changed, 10 insertions(+), 12 deletions(-) diff --git a/website/content/docs/concepts/filtering/events.mdx b/website/content/docs/concepts/filtering/events.mdx index f1f1e8028..2220d9dbb 100644 --- a/website/content/docs/concepts/filtering/events.mdx +++ b/website/content/docs/concepts/filtering/events.mdx @@ -5,12 +5,10 @@ description: |- How to filter events emitted by Boundary. --- -This page describes how to filter events written to Boundary event sinks. - -~> **Note:** This feature was introduced in Boundary 0.5.0. - # Event Filtering +This page describes how to filter events written to Boundary event sinks. + Starting in Boundary 0.5.0, a variety of event types (error, observation, system, etc) are emitted from Boundary. Boundary events can be emitted in several formats including [cloudevents](https://github.com/cloudevents/spec) and diff --git a/website/content/docs/concepts/filtering/oidc-managed-groups.mdx b/website/content/docs/concepts/filtering/oidc-managed-groups.mdx index 0841f8fd3..441b2b91c 100644 --- a/website/content/docs/concepts/filtering/oidc-managed-groups.mdx +++ b/website/content/docs/concepts/filtering/oidc-managed-groups.mdx @@ -5,16 +5,16 @@ description: |- How to configure filters for managed groups within the OIDC auth method. --- +[filter syntax]: /docs/concepts/filtering + +# OIDC Managed Groups Filtering + This page describes how to use filters with OIDC managed groups. It assumes that the reader is familiar with the general [filter syntax][] as well as with [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html). ~> **Note:** This feature was introduced in Boundary 0.3.0. -[filter syntax]: /docs/concepts/filtering - -# OIDC Managed Groups Filtering - Currently, two blocks of data are available for these filters: - `/token/` contains claims from the JWT returned by the OIDC Identity diff --git a/website/content/docs/concepts/filtering/resource-listing.mdx b/website/content/docs/concepts/filtering/resource-listing.mdx index eca55034a..f35c958bd 100644 --- a/website/content/docs/concepts/filtering/resource-listing.mdx +++ b/website/content/docs/concepts/filtering/resource-listing.mdx @@ -5,6 +5,8 @@ description: |- How to use filter list responses coming back from Boundary. --- +# List Filtering + This page describes how to use filters when listing resources. This can be used to reduce the returned set of resources when performing a list operation. @@ -12,8 +14,6 @@ to reduce the returned set of resources when performing a list operation. affect the database queries generated for the operation and as such is not designed to provide greater efficiency. -# List Filtering - Starting in Boundary 0.1.8, when running a list action, a filter can be specified. It uses the standard [filter syntax](/docs/concepts/filtering) used elsewhere in Boundary. Unless otherwise specified for a given list endpoint, the diff --git a/website/content/docs/concepts/filtering/worker-tags.mdx b/website/content/docs/concepts/filtering/worker-tags.mdx index 2af2cd487..2cd621f0c 100644 --- a/website/content/docs/concepts/filtering/worker-tags.mdx +++ b/website/content/docs/concepts/filtering/worker-tags.mdx @@ -5,13 +5,13 @@ description: |- How to use worker tags to control which workers can handle a given resource. --- +# Worker Tags + This page describes how to use worker tags and filters to control which workers are allowed to handle a given resource. This can be used to control traffic locality. As an example, this can be used to ensure that traffic going into a public cloud is only handled by workers running within that same cloud. -# Worker Tags - Starting in Boundary 0.1.5, a worker can be configured with a set of key/value tags in its configuration file. The keys and values can be any lower-cased printable value. Each key can have more than one value: