-
Notifications
You must be signed in to change notification settings - Fork 7
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
Cu 86bygzkm5 images placement for interoperability proxy identity #289
Cu 86bygzkm5 images placement for interoperability proxy identity #289
Conversation
…environment variable
…ta-file-for-interoperability-layer-openhim' into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
…ta-file-for-identity-access-manager-keycloak' into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
…ta-file-for-openhim-mapping-mediator' into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
…ta-file-for-job-scheduler-ofelia' into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
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.
LGTM! Resolve the merge conflicts
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.
@brett-onions overall looks fine to me, just two comments around the existing console env for the image/version to use
…bility-proxy-identity
…bility-proxy-identity
WalkthroughThe recent changes across the configuration files bring enhanced flexibility and configurability to the OpenHIM services. By transitioning from static values to environment variables, the deployment process gains dynamism. Moreover, with updated image references and refined service replica settings, resource management and scalability are significantly improved. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (13)
- identity-access-manager-keycloak/docker-compose.yml (2 hunks)
- identity-access-manager-keycloak/package-metadata.json (1 hunks)
- interoperability-layer-openhim/docker-compose-mongo.cluster.yml (2 hunks)
- interoperability-layer-openhim/docker-compose-mongo.yml (1 hunks)
- interoperability-layer-openhim/docker-compose.await-helper-mongo.yml (1 hunks)
- interoperability-layer-openhim/docker-compose.await-helper.yml (1 hunks)
- interoperability-layer-openhim/docker-compose.yml (3 hunks)
- interoperability-layer-openhim/package-metadata.json (2 hunks)
- job-scheduler-ofelia/docker-compose.yml (2 hunks)
- job-scheduler-ofelia/package-metadata.json (1 hunks)
- openhim-mapping-mediator/docker-compose.yml (1 hunks)
- openhim-mapping-mediator/package-metadata.json (1 hunks)
- test/cucumber/features/single-mode/recipe.feature (1 hunks)
Files skipped from review due to trivial changes (7)
- interoperability-layer-openhim/docker-compose-mongo.yml
- interoperability-layer-openhim/docker-compose.await-helper-mongo.yml
- interoperability-layer-openhim/docker-compose.await-helper.yml
- job-scheduler-ofelia/docker-compose.yml
- job-scheduler-ofelia/package-metadata.json
- openhim-mapping-mediator/docker-compose.yml
- test/cucumber/features/single-mode/recipe.feature
Additional comments not posted (10)
openhim-mapping-mediator/package-metadata.json (1)
9-9
: Environment variable addition looks good.interoperability-layer-openhim/docker-compose-mongo.cluster.yml (3)
5-9
: Environment variable usage for placement constraints looks good.
12-20
: Environment variable usage for image and placement constraints looks good.
35-43
: Environment variable usage for image and placement constraints looks good.interoperability-layer-openhim/package-metadata.json (1)
10-20
: Environment variable additions and modifications look good.identity-access-manager-keycloak/package-metadata.json (1)
9-16
: Environment variable additions look good.identity-access-manager-keycloak/docker-compose.yml (2)
5-11
: Environment variable usage for image and command arguments looks good.
47-47
: Environment variable usage for placement constraints looks good.interoperability-layer-openhim/docker-compose.yml (2)
28-28
: Environment variable usage for placement constraints looks good.
Line range hint
42-59
: Environment variable usage for image and placement constraints looks good.
…y-identity' of github.com:jembi/platform into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
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.
Actionable comments posted: 0
Out of diff range and nitpick comments (3)
.env.cluster (3)
91-91
: Ensure consistency in naming conventions.Consider using a consistent naming convention for instance variables. For example,
JEMPI_WEB_INSTANCES
could be renamed toJEMPI_WEB_INSTANCE_COUNT
to match the pattern used in other variables.
95-95
: Ensure consistency in naming conventions.Consider using a consistent naming convention for instance variables. For example,
JEMPI_REPMGR_PARTNER_NODES
could be renamed toJEMPI_REPMGR_PARTNER_NODE_LIST
to match the pattern used in other variables.
102-102
: Ensure consistency in naming conventions.Consider using a consistent naming convention for instance variables. For example,
JEMPI_API_INSTANCES
could be renamed toJEMPI_API_INSTANCE_COUNT
to match the pattern used in other variables.
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- .env.cluster (1 hunks)
- client-registry-jempi/swarm.sh (1 hunks)
Files skipped from review due to trivial changes (1)
- client-registry-jempi/swarm.sh
…bility-proxy-identity
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.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- interoperability-layer-openhim/docker-compose.yml (3 hunks)
- interoperability-layer-openhim/package-metadata.json (2 hunks)
Files skipped from review as they are similar to previous changes (2)
- interoperability-layer-openhim/docker-compose.yml
- interoperability-layer-openhim/package-metadata.json
…y-identity' of github.com:jembi/platform into CU-86bygzkm5_Images-Placement-for-Interoperability-proxy-identity
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.
Actionable comments posted: 1
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- test/cucumber/features/cluster-mode/jempi.cluster.feature (3 hunks)
Additional comments not posted (1)
test/cucumber/features/cluster-mode/jempi.cluster.feature (1)
42-42
: Ensure consistency in replica counts.Please verify that the replica counts for all services are correct and consistent with the intended configuration. For example,
openhim-core
andopenhim-console
are set to 3 replicas, while others are set to 1. Ensure this matches the desired setup.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- test/cucumber/features/cluster-mode/jempi.cluster.feature (3 hunks)
Files skipped from review as they are similar to previous changes (1)
- test/cucumber/features/cluster-mode/jempi.cluster.feature
Summary by CodeRabbit
New Features
Enhancements
Removals