Skip to content

Releases: sysdiglabs/terraform-provider-sysdig

v0.5.12

03 Mar 08:17
40a1947
Compare
Choose a tag to compare

Bug Fixes

  • trigger_after_pct not handled correctly in sysdig_monitor_alert_downtime resource (#92)

v0.5.11

15 Feb 07:56
9aae0dc
Compare
Choose a tag to compare

Features

  • New scope parameter for sysdig_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

13 Jan 17:32
5047cdc
Compare
Choose a tag to compare

Features

v0.5.9

12 Jan 10:48
c26f36b
Compare
Choose a tag to compare

Features

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

07 Jan 16:44
6aa5983
Compare
Choose a tag to compare

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 all sysdig_monitor_alert_* resources
    • can_see_infrastructure_events in sysdig_monitor_team
    • can_use_aws_data in sysdig_monitor_team
    • severity in sysdig_secure_policy
    • Also tcp.ports and udp.ports in sysdig_secure_rule_network weren't being created correctly in the backend, thus, creating a network rule with no checked ports.

v0.5.7

07 Jan 09:00
8325d23
Compare
Choose a tag to compare

Features

  • Increased timeout for Lists, Macros and Rules from 30 seconds to 5 minutes. (#68)
  • Added retry strategy to the API HTTP client with backoff, so rate limiting problems could be more easily avoided. (#65)

v0.5.6

17 Nov 08:31
79e97f5
Compare
Choose a tag to compare

Changelog

79e97f5 docs: Update docs with falco rule priority changes (#61)
fba0462 fix: Change falco rule priority to info (#60)

v0.5.5

16 Nov 17:12
5645fb7
Compare
Choose a tag to compare

Changelog

5645fb7 docs: Update note warning message (#58)

v0.5.4

11 Nov 17:17
e751521
Compare
Choose a tag to compare

Changelog

e751521 feat: sysdig_secure_policy now supports killing the container (#57)

v0.5.3

05 Nov 14:47
dc4e154
Compare
Choose a tag to compare

Changelog

dc4e154 fix: Allow severity values 1, 2, 3 and 5 in Policies (#54)