Skip to content

Conversation

@mukulpalit-ibm
Copy link
Contributor

Description

  • Added KMS and EN integration to main module along with the S2S auth policy needed as pre-requisite before creating the integration
  • Updated example/advanced and pr tests to include the integration part
  • Updated fully configurable DA code in order to add KMS and EN integration as well as support cross account KMS integration.
  • Updated IBM catalog.json to include kms and event-notifications as new add-ons

Issue for KMS
Issue for EN

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Add KMS and EN integration to app configuration

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Several comments - lets try be consistent with other modules please.
  • I think the DA should also be creating Event Notifications destinations, topics and email (same way we do in Secrets Manager DA).
  • Since KMS and EN integration is on by default in the DA - we should also enable them in the catalog validation. It means we need to run a prereq script to deploy EN and pipe it into the catalogValidationValues.json.template file. We can re-use our permanent HPCS instance for KMS encryption by setting (see here as example)

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see comments

variable "event_notifications_from_email" {
type = string
description = "The email address used to send any App Configuration event coming via Event Notifications"
default = "[email protected]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where is this info available just for my reference ?

@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

1 similar comment
@mukulpalit-ibm
Copy link
Contributor Author

/run pipeline

@ocofaigh ocofaigh merged commit d578781 into main Sep 15, 2025
2 checks passed
@ocofaigh ocofaigh deleted the 15788-kms-en-integration branch September 15, 2025 11:14
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.11.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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants