You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dbc827b
Browse filesBrowse the repository at this point in the historyBrowse files
ci.datadog-api-spec
committed
Regenerate client from commit 637fe58 of spec repo
Copy file name to clipboardExpand all lines: .generator/schemas/v2/openapi.yaml
+49Lines changed: 49 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -61219,6 +61219,31 @@ components:
61219
61219
- CLOUD_FUNCTION
61220
61220
- CLOUD_RUN_REVISION
61221
61221
- GCE_INSTANCE
61222
+
GCPProjectFilterConfig:
61223
+
description: Configuration for filtering the GCP projects that Datadog monitors, by project ID or by project label.
61224
+
properties:
61225
+
filters:
61226
+
description: |-
61227
+
List of filters matched against the project field set by `type`. Filters support the `*` and `?` wildcards, and a leading `!` makes a filter an exclusion.
61228
+
A project is skipped if it matches any exclusion filter. When inclusion filters are set, a project must also match at least one of them.
61229
+
For `project_id`, each filter is a project ID pattern, such as `prod-*`, with up to 15,000 filters.
61230
+
For `project_label`, each filter is a label in the form `key:value`, such as `env:prod*`, with up to 100 filters. Keys are matched exactly and wildcards apply only to values, so `key:*` matches any value.
Configurations for limiting which of the GCP projects this service account can access are monitored by Datadog, with at most one configuration per type. A project is monitored only if it passes the filters of every configured type. By default, Datadog monitors every project the service account can access.
61384
+
When updating a service account, omit this field to keep the current filters, or send an empty list to remove them.
description: Configurations for GCP location filtering, such as region, multi-region, or zone. Only monitored resources that match the specified regions are imported into Datadog. By default, Datadog collects from all locations.
Configuration for filtering the GCP projects that Datadog monitors, by project ID or by project label.
43
+
44
+
:param filters: List of filters matched against the project field set by ``type``. Filters support the ``*`` and ``?`` wildcards, and a leading ``!`` makes a filter an exclusion.
45
+
A project is skipped if it matches any exclusion filter. When inclusion filters are set, a project must also match at least one of them.
46
+
For ``project_id`` , each filter is a project ID pattern, such as ``prod-*`` , with up to 15,000 filters.
47
+
For ``project_label`` , each filter is a label in the form ``key:value`` , such as ``env:prod*`` , with up to 100 filters. Keys are matched exactly and wildcards apply only to values, so ``key:*`` matches any value.
48
+
:type filters: [str], optional
49
+
50
+
:param type: The GCP project field that the filters are matched against.
:param project_filter_configs: Configurations for limiting which of the GCP projects this service account can access are monitored by Datadog, with at most one configuration per type. A project is monitored only if it passes the filters of every configured type. By default, Datadog monitors every project the service account can access.
135
+
When updating a service account, omit this field to keep the current filters, or send an empty list to remove them.
:param region_filter_configs: Configurations for GCP location filtering, such as region, multi-region, or zone. Only monitored resources that match the specified regions are imported into Datadog. By default, Datadog collects from all locations.
0 commit comments