Skip to content

[CBTL-2670] Add additional business group ID #40

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

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

hoangmirs
Copy link
Collaborator

@hoangmirs hoangmirs commented Mar 19, 2025

What happened 👀

  • Add SECONDARY_BUSINESS_GROUP_ID to support download assets from the secondary exchange. In our case, CBTL would like to use the common-module from GT
  • Update version for all workflows to use the newest one

Insight 📝

Proof Of Work 📹

N/A

@hoangmirs hoangmirs added the type : chore Chore label Mar 19, 2025
@hoangmirs hoangmirs self-assigned this Mar 19, 2025
@hoangmirs hoangmirs marked this pull request as ready for review March 19, 2025 16:00
Copy link
Member

@andyduong1920 andyduong1920 left a comment

Choose a reason for hiding this comment

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

A small comment, also can we find some other name for SECONDARY_BUSINESS_GROUP_ID @hoangmirs - how about UPSTREAM_BUSINESS_GROUP_ID 🤔

@@ -69,6 +69,8 @@ on:
required: false
BUSINESS_GROUP_ID:
required: true
SECONDARY_BUSINESS_GROUP_ID:
Copy link
Member

Choose a reason for hiding this comment

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

Hi @hoangmirs can you explain a bit on this idea as we didn't consume the SECONDARY_BUSINESS_GROUP_ID in this workflow, why do we need to add it here? 🤔

Or you are missing it in uses: nimblehq/mulesoft-actions/deploy_cloudhub_1_0@v1.23.0 step?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@andyduong1920 This enables us to define the repositories here for the app to download.
image
So, from my understanding, whenever we build the app (in test or deploy workflows), we will need to add it so that the app can have access to the correct repository to download the assets (documentation or modules).
For the name, SECONDARY_BUSINESS_GROUP_ID I chose it as this is not the main business group ID of the app, but another one that the app need to fetch the modules, in this case, the GT one. Same for GT app, later we might need to download from other services (maybe from JFC), so I don't think we should name it as UPSTREAM_BUSINESS_GROUP_ID.
For the naming, can we name it as ADDITIONAL_BUSINESS_GROUP_ID?

@andyduong1920
Copy link
Member

@hoangmirs btw, Instead of putthing this new configuration, can you use the GT's BUSINESS_GROUP_ID directly in the CBTL's codebase -- because the BUSINESS_GROUP_ID isn't a sensitive information at all 🤔

@hoangmirs
Copy link
Collaborator Author

@hoangmirs btw, Instead of putthing this new configuration, can you use the GT's BUSINESS_GROUP_ID directly in the CBTL's codebase -- because the BUSINESS_GROUP_ID isn't a sensitive information at all 🤔

Is it ok to put it as hard-coded? I also want to to that so that we don't need to pass it through a few steps like the current one 🤔

@andyduong1920
Copy link
Member

@hoangmirs btw, Instead of putthing this new configuration, can you use the GT's BUSINESS_GROUP_ID directly in the CBTL's codebase -- because the BUSINESS_GROUP_ID isn't sensitive information at all 🤔

Is it ok to put it as hard-coded? I also want to to that so that we don't need to pass it through a few steps like the current one 🤔

yes @hoangmirs as that is not sensitive information - and we have that in the app, for example, you can check the codebase like

image

@hoangmirs hoangmirs marked this pull request as draft March 20, 2025 03:26
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.

2 participants