RC candidate for the next Mojaloop release (post v15.1.0)

[elnyry-sam-k]

Goal:

As a ML OSS adopter

I want to have an Release Candidate for a post ML v15.1.0 that is successfully validated by the Golden path tests and ready for a release

so that I can start the validation processes prior to adopting the release based on this RC

Acceptance Criteria:

• Confirm the version number of the next Mojaloop release based on the changes included
• Helm RC Release is validated on Moja2 to achieve 100% result with TTK GoldenPath
• Helm RC Release is validated with PISP provisioning and test collection (TTK) with 100%
• Helm RC Release is validated with Bulk test collection (TTK) with 100%
• QA (Golden path) on deployments done on AWS Moja2 environment is done
• Bugs are logged based on observations, failures
• Bugs logged are fixed if critical / blockers to make subsequent releases in individual services (or Helm)
• Release notes are drafted (to be published with the helm release)
• Test cases on a RC branch are created and validated
• TTK tests run successfully as Post-Hook jobs and Tests

Notes:

• This story is for creating a stable Release Candidate based on which the release will be made

Complexity: Medium - Involves all core and supporting services
Uncertainty: Medium

---

Tasks:

• Initial PR with changes for RC @oderayi
  • Initial PR review @mdebarros @aaronreynoza
  • Deploy, validate, fix issues, redeploy @aaronreynoza @oderayi
  • With stable deployment test Golden path @aaronreynoza @oderayi @sri-miriyala
• Validate PISP test provisioning and test collections (TTK) @aaronreynoza @oderayi
• Identify issues with QA Scripts if any - fix them and retest @aaronreynoza @oderayi @mdebarros
• QA for bugs, regressions, log them @aaronreynoza @oderayi @mdebarros @sri-miriyala
• Fix bugs logged if critical @aaronreynoza @oderayi @mdebarros
• Deploy, validate on AWS Moja2 @aaronreynoza @oderayi
• Validate with TTK GP collection @aaronreynoza @oderayi @sri-miriyala
• TTK test-cases on a RC branch is created and validated @oderayi
• Release notes for helm RC is drafted @aaronreynoza @sri-miriyala
  • Guidance for migration from Release (may have to be a separate story if sufficiently big / complex) @aaronreynoza @sri-miriyala
• Update release notes with Upgrade Strategy Guide link @aaronreynoza @sri-miriyala
• Deployment of RC on Moja2 (or one of the moja environments) @oderayi @aaronreynoza
  • RC is deployed on Moja2 successfully
  • Regression testing on Moja2 using TTK collections @aaronreynoza @oderayi
    • GP collection
    • Core Bulk collection
    • Third-party collection
    • SDK Bulk collection
    • SDK R2P collection
  • Validation using CGS Golden path regression tests etc on Moja2
  • Test upgradability from previous release @oderayi

Done

• Acceptance Criteria pass
• Designs are up-to date
• TTK Tests pass
• Code Style & Coverage meets standards
• Release notes are verified

Pull Requests:

• feat(mojaloop/#3533): mojaloop helm release v15.2.0 helm#581
• chore(mojaloop/#3533): fix provisioning delay testing-toolkit-test-cases#127
• chore(mojaloop/#3533): update dependencies thirdparty-api-svc#92
• chore(mojaloop/#3533): update dependencies event-sidecar#55
• chore(mojaloop/#3533): update dependencies central-settlement#396
• fix(mojaloop/#3533): helm v15.2.0-rc fixes central-ledger#982
• fix(mojaloop/#3589): fix mongoose 'promiseLibrary' option bug bulk-api-adapter#102
• fix(mojaloop/#3533): downgrade ML dependencies central-settlement#398
• feat(mojaloop/#3533): v15.2.0 release fixes testing-toolkit-test-cases#128
• feat(mojaloop/#3533): v15.2.0 release fixes testing-toolkit-test-cases#129
• fix(mojaloop/#3604): update dependencies quoting-service#320

Issues:

Follow-up:

Dependencies:

• N/A

Accountability:

• Owner:
• QA/Review: @mdebarros @elnyry-sam-k @vijayg10

[oderayi]

Application versions for the next release:

ml-api-adapter: v14.0.0 --> v14.0.5
central-ledger: v17.0.3 --> v17.3.2
account-lookup-service: v14.1.0 --> v15.0.0
quoting-service: v15.0.2 --> v15.5.0
central-settlement: v15.0.0 --> v16.0.0
bulk-api-adapter: v15.0.3 --> v17.0.0
central-event-processor: v12.0.0 - no new release
email-notifier: v12.0.0 --> v14.0.0
als-oracle-pathfinder: v12.0.0 - no new release
transaction-requests-service: v14.1.0 --> v14.1.2
finance-portal-ui: v10.4.3 (DEPRECATED) - not upgraded in the last release
finance-portal-backend-service: v15.0.2 (DEPRECATED) - not upgraded in the last release
settlement-management: v11.0.0 (DEPRECATED) - no new release
operator-settlement: v11.0.0 (DEPRECATED) - no new release
event-sidecar: v12.0.0 --> v14.0.0
event-stream-processor: v12.0.0-snapshot.7 - no new release
simulator: v12.0.0 - no new release
mojaloop-simulator: v14.0.1 --> v15.0.0
sdk-scheme-adapter: v23.0.1 --> v23.1.1
ml-testing-toolkit: v16.1.1 --> v17.0.0
ml-testing-toolkit-ui: v15.4.0 - no new release
ml-testing-toolkit-client-lib: v.1.2.0
auth-service: v14.0.0 --> v15.0.0
als-consent-oracle: v0.2.0 --> v0.2.2
thirdparty-api-svc: v13.0.2 --> v14.0.0
thirdparty-sdk: v15.1.0 --> v15.1.1

[elnyry-sam-k]

Thanks for this @oderayi , third-party sdk should have a new release.

this story is closed: #3522 and the PR is merged as well, so I'm not sure why the release didn't happen; does the CI config need to be updated?

[oderayi]

Thanks for pointing that out @elnyry-sam-k.
Looks like the release didn't go through after the merge. I will look into this.

[elnyry-sam-k]

thanks @oderayi , appreciate it.

[mdebarros]

test.mojaloop.live has been upgraded from K8s v1.27 to v1.28:

❯ kubectl version
Server Version: version.Info{Major:"1", Minor:"28+", GitVersion:"v1.28.1-eks-43840fb", GitCommit:"5024547cf72fa45c3617e0c3fe3ae9e6b6e8f7e1", GitTreeState:"clean", BuildDate:"2023-09-06T20:55:59Z", GoVersion:"go1.20.7", Compiler:"gc", Platform:"linux/amd64"}