Skip to content

Commit

Permalink
Change target_type to string instead of enum
Browse files Browse the repository at this point in the history
  • Loading branch information
jamie-suse committed Dec 5, 2023
1 parent 12e0b27 commit 3387fdf
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
3 changes: 1 addition & 2 deletions guides/check_definition.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -163,8 +163,7 @@
"additionalProperties": false,
"properties": {
"target_type": {
"type": "string",
"enum": ["host", "cluster"]
"type": "string"
}
},
"patternProperties": {
Expand Down
4 changes: 2 additions & 2 deletions guides/specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -250,13 +250,13 @@ A key-value map that enriches the Check being declared by providing extra inform

- keys must be non empty strings (`foo`, `bar`, `foo_bar`, `qux1`)
- values can be any of the following types `string`, `number`, `boolean`, `string[]` (list of strings)
- `target_type` is a **required** key of the `metadata` map. It's value can be either a `host` or `cluster`.
- `target_type` is a **required** key of the `metadata` map. It's value is a `string`.

Example:

```yaml
metadata:
target_type: host
target_type: example_target
foo: bar
bar: 42
baz: true
Expand Down

0 comments on commit 3387fdf

Please sign in to comment.