v3.4.0

3.4.0 (2024-12-18)

Features

• updates to the metrics_router_settings input:
  • default_targets, permitted_target_regions, primary_metadata_region, backup_metadata_region and backup_metadata_region are all now optional.
• updates to metrics_router_routes input:
  • action and targets are now both optional.
    • action defaults to "send" if no value passed.
    • targets is not required if the action is "drop".
• Updates to the metrics_router_targets input:
  • target_region is now optional.

(#611) (099276a)

v3.3.1

3.3.1 (2024-11-05)

Bug Fixes

• wait 30 seconds after auth policy is created before creating metrics router target to ensure auth policy is fully in place before proceeding (#604) (4364b44)

v3.3.0

3.3.0 (2024-10-30)

Features

• add support for metrics routing Learn more (#599) (4d602ba)

v3.2.0

3.2.0 (2024-10-29)

Features

• added support to specify Cloud Logs policies using new input cloud_logs_policies (#600) (17dbaaf)

v3.1.1

3.1.1 (2024-10-25)

Bug Fixes

• remove ibm_iam_account_settings from cloud logs module so that account admin access is not required (#589) (b11fe92)

v3.1.0

3.1.0 (2024-10-17)

Features

• added support to create and use s2s auth policy for ATracker to Event Streams service (#584) (7cbc21e)

v3.0.2

3.0.2 (2024-10-15)

Bug Fixes

• add wait/depends on for cos auth policy (#588) (fb320fd)

v3.0.1

3.0.1 (2024-10-10)

Bug Fixes

• updated the service_endpoints input of the cloud_monitoring submodule to only allow the value public-and-private. Previouslly it incorrectly allowed values of public and private however it is not possible to create public only or private only Cloud Monitoring instances (#583) (d1ed5cf)

v3.0.0

3.0.0 (2024-10-08)

Features

• fully remove Log Analysis and Activity Tracker support (#582) (6b88ba2)

BREAKING CHANGES

• Log Analysis and Activity Tracker support has been removed from this module since those services are deprecated and replace by IBM Cloud Logs and ATracker routes.

⚠️ If you have archiving enabled for your Log Analysis or Activity Tracker instances, you need to ensure to disable it before attempting to destroy the instances (which is what will happen when you upgrade to v3.0.0), otherwise you will end up with an error that says: expected either servicekey or iamtoken to be set. This happens because you cannot destroy the resource key and disable log archiving in the same plan since the resource key is used to initialise the logdna provider which is used for archiving. Once it has been disabled, you can proceed with instance destroy.

v2.19.1

2.19.1 (2024-09-30)

Bug Fixes

• fix cycle error (#577) (4870caa)