Releases: sysdiglabs/terraform-provider-sysdig
Releases · sysdiglabs/terraform-provider-sysdig
v1.4.1
Changelog
- a4654a7 refactor(policies): refactor policies to use v2 client (#312)
- 0d528b2 refactor(lists): refactor list to use v2 client (#310)
- 1776250 refactor(macro): refactor macro to use new v2 client (#311)
- b1d4bea refactor(notificationchannels): refactor secure notification channels to use v2 client (#309)
- 3593fdb fix policy so that it correctly identifies the default state and does not suggest the resource needs to be updated (#308)
v1.4.0
Changelog
v1.3.0
Changelog
- b27f2dc feat(notificationchannels): add team option in provider, add share_with_current_team in notification channels (#294)
- fb6697d Adding the possibility to run only certain tests per service for Secure (#298)
- 85e14e8 fix[tests]: Fix secure connection tests when run against secure-staging instead of prod (#295)
- e1aeaa3 docs: fix bad example (#296)
v1.2.0
v1.1.0
We added support for IBM Cloud Monitoring authentication with this release. Users can use IBM API key and Instance ID to authenticate against IBM Cloud Monitoring. Since this new authentication is still under active development we are going to iteratively enable it for each terraform resource starting with teams. Users on IBM monitor application can use previously mentioned authentication method to manage teams.
Changelog
v1.0.2
Changelog
- 0e4534b Add Provider Header to All Secure Requests (#280)
- 0234a9e Remove tee comand from output as it was overrinding the final result (#278)
- dbe9488 fix(alerts): remove hardcoded ids in tests (#284)
- 8d92c94 fix(policy): fix actions to not apply different schema on actions in state (#281)
- 9cc9632 add description to rule as falco validation requires a description (#279)
v1.0.1
Summary:
Drifts created by manually disabling/enabling (eg. via UI) capture on sysdig_secure_policy are now recognized by provider and will report them in terraform plan.