Skip to content

Conversation

@rajatagarwal-ibm
Copy link
Member

Description

Release required?

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

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.

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.

I left a few comments. We had a call with the docs team on Friday, and all of these types of PRs need to be reviewed by the docs team since they are adding / updating content that will be shown in the tile (descriptions, features etc etc)

},
{
"name": "deploy-arch-ibm-observability",
"description": "Enable to provisions and configures IBM Cloud Monitoring, Activity Tracker, and Log Analysis services for analysing events generated from the Events Notification instance.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Description need to be fixed. It is inaccurate and referencing deprecated service. See the update I made in EN DA. But also docs team should review final proposal.

Choose a reason for hiding this comment

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

Do you have a link to your proposal?

Copy link
Contributor

Choose a reason for hiding this comment

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

@rajatagarwal-ibm
Copy link
Member Author

I have left all the documentation comments, as I believe each one of these + any other docs related comment can be addressed in a separate PR

@rajatagarwal-ibm
Copy link
Member Author

/run pipeline

@rajatagarwal-ibm rajatagarwal-ibm changed the title Sm addon migration DO NOT MERGE: Sm addon migration May 26, 2025
@rajatagarwal-ibm rajatagarwal-ibm marked this pull request as draft May 26, 2025 15:10
Copy link

@smguilia smguilia left a comment

Choose a reason for hiding this comment

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

There are some common issues to be on the lookout for in future PRS:

  1. Use the legally approved service names. Verify that they're on this list: https://github.ibm.com/cloud-doc-build/markdown/blob/master/cloudoekeyrefs.yml

  2. Be sure you're not dropping words like "The" or "An / a"

  3. Capitalization of Cloud automation for _____ should be consistent.

  4. For the descriptions in the catalog - I would focus more on the benefits of the things deploying in the descriptions rather than just saying that they're integrated or provisioned. Let me know if this one doesn't make sense. I put in several comments but they might not be 100% technically accurate.

@rajatagarwal-ibm rajatagarwal-ibm changed the title DO NOT MERGE: Sm addon migration Sm addon migration May 28, 2025
@rajatagarwal-ibm rajatagarwal-ibm marked this pull request as ready for review May 28, 2025 09:57
rajatagarwal-ibm and others added 8 commits May 28, 2025 11:18
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
Co-authored-by: Shawna Hinger <[email protected]>
@rajatagarwal-ibm
Copy link
Member Author

/run pipeline

@rajatagarwal-ibm
Copy link
Member Author

@smguilia thanks for the review.

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.

Update the variable description for secret_groups to mention about prefix being used in access group name (for both variations).

Also as Steve pointed out yesterday we need to include the information about the default "General" secret group that gets created in more places. Descriptions, Features, Diagram description etc

},
{
"name": "deploy-arch-ibm-observability",
"description": "Enable to provisions and configures IBM Cloud Monitoring, Activity Tracker, and Log Analysis services for analysing events generated from the Events Notification instance.",
Copy link
Contributor

Choose a reason for hiding this comment

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

@rajatagarwal-ibm
Copy link
Member Author

Also as Steve pointed out yesterday we need to include the information about the default "General" secret group that gets created in more places. Descriptions, Features, Diagram description etc

secret group is already part of features and its in the diagram. Not sure what else need to be added in the Description and diagram description, especially around "General" because user can change that value.

SKIP UPGRADE TEST: avoid access group conflict
…/terraform-ibm-secrets-manager into sm-addon-migration
@rajatagarwal-ibm
Copy link
Member Author

/run pipeline

@ocofaigh ocofaigh merged commit 41a72e7 into main May 28, 2025
2 checks passed
@ocofaigh ocofaigh deleted the sm-addon-migration branch May 28, 2025 16:31
@terraform-ibm-modules-ops
Copy link
Contributor

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

6 participants