Skip to content

Commit c6d7e31

Browse files
committed
add md files for new data sources
1 parent d947ce3 commit c6d7e31

File tree

5 files changed

+134
-1
lines changed

5 files changed

+134
-1
lines changed

sysdig/data_source_sysdig_secure_zone_test.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
//go:build tf_acc_sysdig_secure || tf_acc_onprem_secure || tf_acc_ibm_secure
1+
//go:build tf_acc_sysdig_secure || tf_acc_onprem_secure
22

33
package sysdig_test
44

website/docs/d/monitor_team.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
subcategory: "Sysdig Monitor"
3+
layout: "sysdig"
4+
page_title: "Sysdig: sysdig_monitor_team"
5+
description: |-
6+
Retrieves information about a specific monitor team in Sysdig
7+
---
8+
9+
# sysdig_monitor_team
10+
11+
The `sysdig_monitor_team` data source retrieves information about a specific monitor team in Sysdig.
12+
13+
## Example Usage
14+
15+
```terraform
16+
data "sysdig_monitor_team" "example" {
17+
id = "812371"
18+
}
19+
```
20+
21+
## Argument Reference
22+
23+
- `id` - (Required) The ID of the monitor team.
24+
25+
## Attribute Reference
26+
27+
- `name` - The name of the monitor team.
28+
- `description` - The description of the monitor team.
29+
- `entrypoint` - The entrypoint configuration for the team.
30+
- `filter` - The filter applied to the team.
31+
- `scope_by` - The scope of the team.
32+
- `can_use_sysdig_capture` - Whether the team can use Sysdig capture.
33+
- `can_see_infrastructure_events` - Whether the team can see infrastructure events.
34+
- `can_use_aws_data` - Whether the team can use AWS data.
35+
- `default_team` - Whether the team is the default team.
36+
- `user_roles` - The roles assigned to users in the team.

website/docs/d/monitor_teams.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
subcategory: "Sysdig Monitor"
3+
layout: "sysdig"
4+
page_title: "Sysdig: sysdig_monitor_teams"
5+
description: |-
6+
Retrieves information about a specific monitor teams in Sysdig
7+
---
8+
9+
# sysdig_monitor_teams
10+
11+
The `sysdig_monitor_teams` data source retrieves a list of all monitor teams in Sysdig.
12+
13+
## Example Usage
14+
15+
```terraform
16+
data "sysdig_monitor_teams" "example" {}
17+
```
18+
19+
## Attribute Reference
20+
21+
- `teams` - A list of monitor teams. Each team has the following attributes:
22+
- `id` - The ID of the monitor team.
23+
- `name` - The name of the monitor team.
24+
- `description` - The description of the monitor team.
25+
- `filter` - The filter applied to the team.
26+
- `scope_by` - The scope of the team.
27+
- `can_use_sysdig_capture` - Whether the team can use Sysdig capture.
28+
- `can_see_infrastructure_events` - Whether the team can see infrastructure events.
29+
- `can_use_aws_data` - Whether the team can use AWS data.
30+
- `default_team` - Whether the team is the default team.
31+
- `user_roles` - The roles assigned to users in the team.

website/docs/d/secure_team.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
subcategory: "Sysdig Secure"
3+
layout: "sysdig"
4+
page_title: "Sysdig: sysdig_secure_team"
5+
description: |-
6+
Retrieves information about a specific secure team in Sysdig
7+
---
8+
9+
# sysdig_secure_team
10+
11+
The `sysdig_secure_team` data source retrieves information about a specific secure team in Sysdig.
12+
13+
## Example Usage
14+
15+
```terraform
16+
data "sysdig_secure_team" "example" {
17+
id = "812371"
18+
}
19+
```
20+
21+
## Argument Reference
22+
23+
- `id` - (Required) The ID of the secure team.
24+
25+
## Attribute Reference
26+
27+
- `name` - The name of the secure team.
28+
- `description` - The description of the secure team.
29+
- `filter` - The filter applied to the team.
30+
- `scope_by` - The scope of the team.
31+
- `use_sysdig_capture` - Whether the team can use Sysdig capture.
32+
- `default_team` - Whether the team is the default team.
33+
- `user_roles` - The roles assigned to users in the team.
34+
- `zone_ids` - The IDs of the zones associated with the team.
35+
- `all_zones` - Whether the team has access to all zones.

website/docs/d/secure_teams.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
subcategory: "Sysdig Secure"
3+
layout: "sysdig"
4+
page_title: "Sysdig: sysdig_secure_teams"
5+
description: |-
6+
Retrieves information about a specific secure teams in Sysdig
7+
---
8+
9+
# sysdig_secure_teams
10+
11+
The `sysdig_secure_teams` data source retrieves a list of all secure teams in Sysdig.
12+
13+
## Example Usage
14+
15+
```terraform
16+
data "sysdig_secure_teams" "example" {}
17+
```
18+
19+
## Attribute Reference
20+
21+
- `teams` - A list of secure teams. Each team has the following attributes:
22+
- `id` - The ID of the secure team.
23+
- `name` - The name of the secure team.
24+
- `description` - The description of the secure team.
25+
- `filter` - The filter applied to the team.
26+
- `scope_by` - The scope of the team.
27+
- `use_sysdig_capture` - Whether the team can use Sysdig capture.
28+
- `default_team` - Whether the team is the default team.
29+
- `user_roles` - The roles assigned to users in the team.
30+
- `zone_ids` - The IDs of the zones associated with the team.
31+
- `all_zones` - Whether the team has access to all zones.

0 commit comments

Comments
 (0)