Skip to content

Conversation

@terraform-ibm-modules-ops
Copy link
Contributor

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

This PR contains the following updates:

Package Type Update Change
terraform-ibm-modules/event-notifications/ibm (source) module minor 1.10.21 -> 1.14.7
terraform-ibm-modules/secrets-manager/ibm (source) module patch 1.18.6 -> 1.18.14

Release Notes

terraform-ibm-modules/terraform-ibm-event-notifications (terraform-ibm-modules/event-notifications/ibm)

v1.14.7

Compare Source

Bug Fixes
  • deps: update terraform terraform-ibm-modules/cos/ibm to v8.14.5 (#​333) (2d2268d)

v1.14.6

Compare Source

Bug Fixes

v1.14.5

Compare Source

Bug Fixes
  • deps: update terraform ibm to latest for the deployable architecture solution (#​330) (d19b633)

v1.14.4

Compare Source

Bug Fixes
  • updated the value of kms_endpoint_url to old HPCS endpoint (#​328) (09046bb)

v1.14.3

Compare Source

Bug Fixes

v1.14.2

Compare Source

Bug Fixes
  • deps: updated KMS module to 4.16.4 in the DA solution (#​320) (ef2b9a4)

v1.14.1

Compare Source

Bug Fixes
  • deps: update required_provider to latest for the deployable architecture solution (#​317) (1af89b9)

v1.14.0

Compare Source

Features
  • The COS KMS auth policy created by the DA is now scoped to the exact KMS key. NOTE: When upgrading from an old version, the auth policy will be re-created, however it will be non disruptive as it will create the new policy before removing the old one (#​324) (8247228)

v1.13.1

Compare Source

Bug Fixes
  • update SCC profile to IBM Cloud Framework for Financial Services 1.7.0 (#​319) (89c50a7)

v1.13.0

Compare Source

Features
  • Updated the KMS auth policies created by the module and DA to now scope them to the exact KMS Key ID. Previously auth policies were scoped to the whole KMS instance. This change has been implemented in a way where it will create the new auth policy first before destroying the old one to ensure there is no disruption to every day operations.
  • updated the configuration in the DA that is used to stored failed events in a COS bucket to now use the direct COS endpoint by default (previously it was using the public endpoint). This change is done as an update in place. (#​313) (80b244f)

v1.12.0

Compare Source

Features
  • Since Activity Tracker is a deprecated service, the ability to pass the CRN of an Activity Tracker instance (existing_activity_tracker_crn) in the DA solution to configure the IBM Cloud Object Storage bucket that is used for storing failed events has been removed. Events are now sent according to what is specified in the accounts ATracker Event Routing service configuration. This change will cause an update in place on the COS bucket if using the DA to create one. (#​316) (85b939d)

v1.11.0

Compare Source

Features
  • added support to the DA to create service credentials and manage them in Secrets Manager (#​266) (3171580)

v1.10.23

Compare Source

Bug Fixes
  • deps: update terraform ibm to latest for the deployable architecture solution (#​310) (5ddecab)

v1.10.22

Compare Source

Bug Fixes
terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)

v1.18.14

Compare Source

Bug Fixes
  • deps: update terraform terraform-ibm-modules/event-notifications/ibm to v1.14.4 (#​230) (b300e61)

v1.18.13

Compare Source

Bug Fixes

v1.18.12

Compare Source

Bug Fixes

v1.18.11

Compare Source

Bug Fixes

v1.18.10

Compare Source

Bug Fixes
  • update to SCC profile IBM Cloud Framework for Financial Services 1.7.0 (#​217) (69b8bf9)

v1.18.9

Compare Source

Bug Fixes
  • fixed the value of the resource_group_id output in the DA solution (#​216) (fe3a95c)

v1.18.8

Compare Source

Bug Fixes
  • deps: update terraform ibm to latest for the deployable architecture solution (#​212) (8d2e521)

v1.18.7

Compare Source

Bug Fixes
  • deps: upgraded version of secrets-manager-iam-engine to 1.2.3 to fix issue (#​213) (28996ce)

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

@terraform-ibm-modules-ops terraform-ibm-modules-ops changed the title chore(deps): update terraform terraform-ibm-modules/event-notifications/ibm to v1.10.22 chore(deps): update terraform-module Oct 11, 2024
@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev

/run pipeline

@terraform-ibm-modules-dev terraform-ibm-modules-dev merged commit 00133fe into main Nov 23, 2024
2 checks passed
@terraform-ibm-modules-dev terraform-ibm-modules-dev deleted the renovate/terraform-module branch November 23, 2024 03:52
@terraform-ibm-modules-ops
Copy link
Contributor Author

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

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.

3 participants