Skip to content

Conversation

@terraform-ibm-modules-ops
Copy link
Contributor

@terraform-ibm-modules-ops terraform-ibm-modules-ops commented Oct 12, 2024

This PR contains the following updates:

Package Type Update Change
terraform-ibm-modules/observability-instances/ibm (source) module major 2.17.0 -> 3.3.1

Release Notes

terraform-ibm-modules/terraform-ibm-observability-instances (terraform-ibm-modules/observability-instances/ibm)

v3.3.1

Compare Source

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

Compare Source

Features

v3.2.0

Compare Source

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

v3.1.1

Compare Source

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

v3.1.0

Compare Source

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

v3.0.2

Compare Source

Bug Fixes

v3.0.1

Compare Source

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

Compare Source

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

Compare Source

Bug Fixes

v2.19.0

Compare Source

Features (#​576) (db5a58f)
  • add support to enable platform logs with a boolean for cloud logs
  • The module no longer deploys the deprecated services Log Analysis or Activity Tracker by default
    • log_analysis_provision is now false by default
    • activity_tracker_provision is now false by default

v2.18.1

Compare Source

Bug Fixes
  • update Cloud Monitoring service endpoint variable description (#​572) (84c1143)

v2.18.0

Compare Source

Features
  • added support to Cloud Logs module to create log routing teneants that targets the Cloud Logs instance created by the module. To manage platform logs that are generated by IBM Cloud® services in a region of IBM Cloud, you must create a tenant in each region that you operate. (#​559) (a65ec6d)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@terraform-ibm-modules-dev

/run pipeline

2 similar comments
@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-terraform-module branch from f92a481 to 91a650c Compare October 19, 2024 00:59
@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-terraform-module branch from 91a650c to c5f987a Compare October 26, 2024 04:24
@terraform-ibm-modules-dev

/run pipeline

1 similar comment
@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-terraform-module branch from c5f987a to 3f77458 Compare November 2, 2024 02:59
@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops force-pushed the renovate/major-terraform-module branch from 3f77458 to ecd9fa0 Compare November 9, 2024 03:12
@terraform-ibm-modules-dev

/run pipeline

1 similar comment
@terraform-ibm-modules-dev

/run pipeline

@shemau
Copy link
Contributor

shemau commented Nov 18, 2024

/run pipeline

@ocofaigh ocofaigh merged commit 444131c into main Nov 18, 2024
2 checks passed
@ocofaigh ocofaigh deleted the renovate/major-terraform-module branch November 18, 2024 09:32
@terraform-ibm-modules-ops
Copy link
Contributor Author

🎉 This PR is included in version 1.4.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants