Releases: sysdiglabs/terraform-provider-sysdig
Releases · sysdiglabs/terraform-provider-sysdig
v1.5.0
Changelog
- 68f8259 feat(policies): Data Source for managed policies (#333)
- 7f65882 Add Miguel as codeowner for policies service (#325)
- c748066 feat(policies): Resource for Secure managed ruleset (#326)
- 453bff8 fix(client): revert sysdig provider header back (#332)
- daebb24 refactor(users): update user tests to craete user with qa-robot inside name (#328)
- 94d0e10 refactor(tests): add tf_acc_policies tag in common_test (#330)
- 8c9970d tests: Fix test execution param order (#329)
- 63e69ba Refactor dashboard (#323)
- d74a83e feat(policies): add resource for managing the configuration of secure managed policies (#316)
- 8b1bdf5 add detection backend team members to codeowners (#324)
v1.4.2
Changelog
- 2206171 refactor(cloudaccount): remove monitor client, refactor to v2 (#319)
- 1f5c356 refactor(cloudaccount): refactor cloud account in secure to v2 (#318)
- 4b2db5c Refactor scanningpolicies (#317)
- 8cb6254 refactor(vulexception): refactor vulexception to v2 client (#315)
- 70e466a refactor(rule): refactor rules to use v2 client (#314)
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.