Skip to content

Feature/cdapi 144#131

Merged
samdasari11 merged 11 commits intomainfrom
feature/CDAPI-144
Apr 30, 2026
Merged

Feature/cdapi 144#131
samdasari11 merged 11 commits intomainfrom
feature/CDAPI-144

Conversation

@samdasari11
Copy link
Copy Markdown
Contributor

Description

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming
  • Exceptions/Exclusions to coding standards (e.g. #noqa or #NOSONAR) are included within this Pull Request.

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

Copy link
Copy Markdown

@williamjameswillis williamjameswillis left a comment

Choose a reason for hiding this comment

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

added some comments also my AI pointed out the following extras:

'The ticket explicitly requires: "Verify observability (logs, correlation IDs, traceability across systems)". No test in the IntEnvi suite checks response headers for a correlation ID (e.g. x-correlation-id). This is a direct gap against the acceptance criteria.'

There is no IntEnvi test for:

A missing Bearer token → expected HTTP 401
An invalid/expired Bearer token → expected HTTP 401

INTEGRATION.bru environment file is incomplete
environments/INTEGRATION.bru only declares secret variable names (PRIVATE_KEY_PATH, KID, PR_NUMBER, JWT_SECRET). However, Get_Auth_Token.bru uses {{APIM_ENV}} in its URL, which is not defined in the INTEGRATION environment. Running the auth token fetch against the integration environment will fail unless this is configured separately.

Comment thread bruno/APIM/Test_MNS_Service_Experience_Validation_Error_IntEnvi.bru
Comment thread bruno/APIM/Test_MNS_Service_Returns_Client_Side_Error_IntEnvi.bru
Comment thread bruno/APIM/Test_PDM_Api_Validation_Error.bru
Comment thread bruno/APIM/Test_PDM_Bundle_Succesful_Response_IntEnvi.bru
Comment thread bruno/APIM/Test_Document_Bundle_via_APIM_IntEnvi.bru
Comment thread bruno/APIM/Test_Document_Bundle_via_APIM_IntEnvi.bru
@samdasari11
Copy link
Copy Markdown
Contributor Author

added some comments also my AI pointed out the following extras:

'The ticket explicitly requires: "Verify observability (logs, correlation IDs, traceability across systems)". No test in the IntEnvi suite checks response headers for a correlation ID (e.g. x-correlation-id). This is a direct gap against the acceptance criteria.'

There is no IntEnvi test for:

A missing Bearer token → expected HTTP 401 An invalid/expired Bearer token → expected HTTP 401

INTEGRATION.bru environment file is incomplete environments/INTEGRATION.bru only declares secret variable names (PRIVATE_KEY_PATH, KID, PR_NUMBER, JWT_SECRET). However, Get_Auth_Token.bru uses {{APIM_ENV}} in its URL, which is not defined in the INTEGRATION environment. Running the auth token fetch against the integration environment will fail unless this is configured separately.

Added relevant logs from Cloudwatch on the ticket.
Added tests for missing Auth token and Expired Auth token

@samdasari11 samdasari11 marked this pull request as ready for review April 28, 2026 08:46
@samdasari11 samdasari11 requested a review from a team as a code owner April 28, 2026 08:46
Copy link
Copy Markdown

@williamjameswillis williamjameswillis left a comment

Choose a reason for hiding this comment

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

re-approving after fixing the signed commit issue

@sonarqubecloud
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

Deployment Complete

@samdasari11 samdasari11 merged commit 21fc2be into main Apr 30, 2026
39 checks passed
@samdasari11 samdasari11 deleted the feature/CDAPI-144 branch April 30, 2026 12:37
samdasari11 added a commit that referenced this pull request May 1, 2026
)

<!-- markdownlint-disable-next-line first-line-heading -->
## Description

<!-- Describe your changes in detail. -->

## Context

<!-- Why is this change required? What problem does it solve? -->

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ ] Refactoring (non-breaking change)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [ ] I have followed the code style of the project
- [ ] I have added tests to cover my changes
- [ ] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming
- [ ] Exceptions/Exclusions to coding standards (e.g. #noqa or #NOSONAR)
are included within this Pull Request.

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [ ] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.
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.

2 participants