Skip to content

Conversation

@pvsaidurga
Copy link
Contributor

@pvsaidurga pvsaidurga commented Dec 18, 2025

Summary by CodeRabbit

  • Chores
    • Updated chart versions from 1.7.0-develop to 1.7.1-develop across deployment configurations.
    • Updated container image registries and tags for esignet, esignet-ui, and postgres services.
    • Standardized image tag naming across Docker Compose and Helm deployment files.

✏️ Tip: You can customize this high-level summary in your review settings.

Signed-off-by: pvsaidurga <saidurgacsea@gmail.com>
@coderabbitai
Copy link

coderabbitai bot commented Dec 18, 2025

Walkthrough

This PR updates deployment configuration files, bumping Helm chart versions to 1.7.1-develop and switching Docker image registries from mosipid/mosipdev to mosipqa. Image tags are updated to 1.7.x format across Helm values, installation scripts, and docker-compose configurations.

Changes

Cohort / File(s) Summary
Helm Chart Versions
helm/esignet/Chart.yaml, helm/oidc-ui/Chart.yaml
Chart version bumped from 1.7.0-develop to 1.7.1-develop
Helm Values – Image Configuration
helm/esignet/values.yaml, helm/oidc-ui/values.yaml
Image repository switched from mosipid/mosipid to mosipqa and tags updated from 1.7.0 to 1.7.x
Deployment Installation Scripts
deploy/esignet-with-plugins/install.sh, deploy/esignet/install.sh, deploy/oidc-ui/install.sh, deploy/postgres/install.sh
CHART_VERSION bumped to 1.7.1-develop; image repositories updated to mosipqa and tags adjusted to 1.7.x
Docker Compose
docker-compose/docker-compose.yml
Service images updated: mosipdev/mosipdevmosipqa registry; tag format changed from release-1.7.x to 1.7.x

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Homogeneous configuration changes across multiple files (repetitive registry and tag updates)
  • No logic modifications or control-flow changes
  • Straightforward version bumps and image reference updates

Possibly related PRs

Suggested reviewers

  • ase-101
  • Prafulrakhade

Poem

🐰 A hop, skip, and jump through the registry
From mosipid to mosipqa, oh what clarity!
Chart versions rise to 1.7.1,
Tags dance in their new 1.7.x sun,
Deployment configs polished and spry!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately reflects the main changes: it updates multiple Helm chart versions from 1.7.0-develop to 1.7.1-develop across multiple deployment files and manifests.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a 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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
helm/oidc-ui/values.yaml (1)

315-315: Inconsistent registry reference.

The volumePermissions.image.repository still references mosipid/os-shell, while the main image has been migrated to the mosipqa registry. This inconsistency should be addressed to align with the PR's objective of migrating from mosipid/mosipdev to mosipqa.

🔎 Apply this diff to align the registry reference:
-    repository: mosipid/os-shell
+    repository: mosipqa/os-shell
🧹 Nitpick comments (1)
helm/esignet/values.yaml (1)

55-56: Use a fixed version tag instead of the floating 1.7.x reference for deployment reproducibility.

The 1.7.x tag is a floating reference that may resolve to different patch versions over time, affecting deployment consistency. Consider pinning to a specific version tag (e.g., 1.7.0, 1.7.1) or using an image digest hash for guaranteed reproducibility.

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 878d3c7 and 683f749.

📒 Files selected for processing (9)
  • deploy/esignet-with-plugins/install.sh (1 hunks)
  • deploy/esignet/install.sh (2 hunks)
  • deploy/oidc-ui/install.sh (1 hunks)
  • deploy/postgres/install.sh (1 hunks)
  • docker-compose/docker-compose.yml (2 hunks)
  • helm/esignet/Chart.yaml (1 hunks)
  • helm/esignet/values.yaml (1 hunks)
  • helm/oidc-ui/Chart.yaml (1 hunks)
  • helm/oidc-ui/values.yaml (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: Ivanmeneges
Repo: mosip/esignet PR: 1565
File: deploy/keycloak/install.sh:28-29
Timestamp: 2025-12-04T10:54:26.400Z
Learning: The Docker image mosipid/postgresql with tags like 14.2.0-debian-10-r70 is available in the MOSIP ID registry and is used for PostgreSQL deployments in MOSIP projects.
📚 Learning: 2025-12-18T04:10:45.874Z
Learnt from: abhishek8shankar
Repo: mosip/esignet PR: 1581
File: deploy/delete-all.sh:14-14
Timestamp: 2025-12-18T04:10:45.874Z
Learning: In the deploy/delete-all.sh script for the esignet repository, the esignet-softhsm release should be deleted from the "esignet" namespace (not from the "softhsm" namespace), so the hardcoded namespace is intentional.

Applied to files:

  • deploy/esignet/install.sh
  • deploy/esignet-with-plugins/install.sh
📚 Learning: 2025-12-04T10:54:26.400Z
Learnt from: Ivanmeneges
Repo: mosip/esignet PR: 1565
File: deploy/keycloak/install.sh:28-29
Timestamp: 2025-12-04T10:54:26.400Z
Learning: The Docker image mosipid/postgresql with tags like 14.2.0-debian-10-r70 is available in the MOSIP ID registry and is used for PostgreSQL deployments in MOSIP projects.

Applied to files:

  • deploy/postgres/install.sh
  • docker-compose/docker-compose.yml
  • helm/oidc-ui/values.yaml
  • helm/esignet/values.yaml
🔇 Additional comments (8)
helm/esignet/Chart.yaml (1)

5-5: LGTM!

The chart version bump to 1.7.1-develop is consistent with the broader version update across the deployment artifacts.

deploy/esignet-with-plugins/install.sh (1)

11-11: LGTM!

The chart version update aligns with the corresponding Chart.yaml version bump to 1.7.1-develop.

deploy/oidc-ui/install.sh (1)

42-42: LGTM!

The chart version update is consistent with the helm/oidc-ui/Chart.yaml version bump to 1.7.1-develop.

helm/oidc-ui/Chart.yaml (1)

5-5: LGTM!

The chart version bump to 1.7.1-develop maintains consistency across Helm charts in this PR.

deploy/esignet/install.sh (1)

26-26: LGTM!

The chart version update to 1.7.1-develop aligns with the Helm chart version bump.

docker-compose/docker-compose.yml (1)

36-36: Verify image availability before deployment.

The esignet service image has been updated to mosipqa/esignet-with-plugins:1.7.x. Confirm this image exists in the mosipqa registry and is accessible. Run docker manifest inspect mosipqa/esignet-with-plugins:1.7.x to verify availability. If unavailable, adjust to a valid version tag.

deploy/postgres/install.sh (1)

50-50: Verify image availability in the mosipqa registry before deployment.

The PostgreSQL image repository has been switched from mosipid to mosipqa. Ensure that mosipqa/postgresql:14.2.0-debian-10-r70 exists and is accessible in the mosipqa registry before deploying, as registry migrations can introduce image availability issues.

helm/oidc-ui/values.yaml (1)

54-55: Verify Docker image availability and clarify the 1.7.x tag format.

The tag has been changed to 1.7.x, which is non-standard for Docker images. While this tag appears consistently across the project (including in Dockerfile references to release-1.7.x branches and deployment scripts), Docker image tags typically use specific versions (e.g., 1.7.0, 1.7.1) or keywords (e.g., latest, develop).

Before deployment, confirm:

  1. The image mosipqa/oidc-ui:1.7.x exists and is accessible in the registry.
  2. Whether 1.7.x is a literal tag, a shorthand for a specific release version, or should reference a different format (e.g., 1.7.0).

@pvsaidurga pvsaidurga closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant