[CSI-1829] Improve release propagation

[PaulGregoryBaker]

Migrated from Jira: CSI-1829

Original Issue Details:

• Issue Type: Story
• Priority: Medium
• Status: In Progress
• Reporter: Kalin Krustev
• Assignee: Kalin Krustev
• Created: 23/09/2025

---

During a recent upgrade of the AWS pre-prod environment to the latest release a number of items were discovered, which should be improved for the next release:

• [status] The dev profile was active in the environment, which is not a desired state (due to exposing of TTK, debug logging, etc.) and must be removed from there.
• [status] After inspecting this profile it was found that Open Telemetry (OTEL) is part of it. It is likely that we want to have OTEL everywhere, so we should move it to another profile
• [status] The file pm4ml-values-override includes URL to the response rules. This URL is hard to maintain manually when upgrading, so it must be avoided or moved elsewhere (profile or addon)
• The mojaloop and mcm namespaces were failing to sync some annotations and labels. A permanent solution must be implemented in IAC or a KB article for resolving this.
• [status] The file pm4ml-values-override includes the code below, which should be moved to a profile:```
  management-api:
  env:
  ENABLE_UI_API_SERVER: true

- [status] App linting is not enabled in AWS. As a minimum a render and YAML linting must be enabled. Options for running `kube-validate` can be discussed and described in a story.
- [status]  The profile `comesa-pm` is still not part of the release tagging and it should be included. This can happen by including COMESA GP in the release tagging criteria after it has passed in dev.
- [status] Avoid multi-attach issue for the comesa-test-runner deployment
- [status] Create basic process for maintaining release notes

[PaulGregoryBaker]

Comment by Kalin Krustev on 24/09/2025:

• fix: allow partial linting in cloud deployment mojaloop/iac-modules#776
• Link