- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3
feat: Add KMS and EN integration #279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| /run pipeline | 
There was a problem hiding this 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.templatefile. We can re-use our permanent HPCS instance for KMS encryption by setting (see here as example)
There was a problem hiding this 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]" | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
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 ?
| /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
| 🎉 This PR is included in version 1.11.0 🎉 The release is available on: 
 Your semantic-release bot 📦🚀 | 
Description
Issue for KMS
Issue for EN
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers