Releases: sysdiglabs/terraform-provider-sysdig
Releases · sysdiglabs/terraform-provider-sysdig
v0.5.12
v0.5.11
Features
- New
scope
parameter forsysdig_monitor_dashboard
resources that allows to define the global scope of a dashboard and assign PromQL variables. (#90) - Add user provisioning without email confirmation for the
sysdig_user
resource. (#87)
Bug Fixes
- Solve crash when updating Dashboard v3 (#89)
- Solve Monitor alert import and vuln exception removal (#83)
- Improve Monitor Alert condition regexp (#86)
Continuous Integration
- Update stale action to v3 (#81)
Documentation
- Fix a couple of typos in doc page (#88)
Release
- Bump required Go version to 1.15 (#91)
v0.5.10
Features
- New resource:
sysdig_secure_vulnerability_exception_list
. Creates a Sysdig Secure Vulnerability Exception list that will hold all the vulnerability exceptions. - New resource:
sysdig_secure_vulnerability_exception
. Creates a Sysdig Secure Vulnerability Exception. - New data source:
sysdig_user
. Retrieves information about a user from their email.
v0.5.9
Features
- Added support for "text" panel types for Dashboard resources. (#77) See example in the official documentation
- Added custom notification config for Monitor alerts. (#71) See documentation
Continuous Integration
- Added automatic cleaning on stale issues and PRs. Now issues and PRs older than 60 days will be marked as Stale, and closed after 7 days. (#52)
- Parallelize tests. With the new HTTP retry strategy, we can parallelize the tests while avoiding API quota errors. (#76)
Bug Fixes
- Solved a crash when importing dashboard with unsupported panel types and query types. (#73)
v0.5.8
Features
- Import resources (#70) (6aa5983)
Terraform is able to import existing infrastructure. This allows you take resources you've created by some other means and bring it under Terraform management.
Bug Fixes
- Solve fields not correctly set (#69) (266b0c6)
Some fields weren't being correctly set when retrieved from the API, like:severity
in allsysdig_monitor_alert_*
resourcescan_see_infrastructure_events
insysdig_monitor_team
can_use_aws_data
insysdig_monitor_team
severity
insysdig_secure_policy
- Also
tcp.ports
andudp.ports
insysdig_secure_rule_network
weren't being created correctly in the backend, thus, creating a network rule with no checked ports.