Skip to content

[CDAPI-119] Initial INT workflow#113

Merged
neil-sproston merged 2 commits intomainfrom
CDAPI-119intWorkflow
Apr 20, 2026
Merged

[CDAPI-119] Initial INT workflow#113
neil-sproston merged 2 commits intomainfrom
CDAPI-119intWorkflow

Conversation

@neil-sproston
Copy link
Copy Markdown
Contributor

@neil-sproston neil-sproston commented Apr 20, 2026

Description

Initial INT workflow

Context

Required to support onging iterative changes

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.

@neil-sproston neil-sproston requested a review from a team as a code owner April 20, 2026 11:44
Copy link
Copy Markdown
Collaborator

@nhsd-jack-wainwright nhsd-jack-wainwright left a comment

Choose a reason for hiding this comment

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

LGTM 👍, just a few small comments / suggestions

Comment on lines +19 to +21
BASE_URL: "https://internal-dev.api.service.nhs.uk/${{ vars.PROXYGEN_API_NAME }}-integration"
ENV: "remote"
HOST: "internal-dev.api.service.nhs.uk"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think BASE_URL and HOST values here will need to be updated to match the INT environment

Suggested change
BASE_URL: "https://internal-dev.api.service.nhs.uk/${{ vars.PROXYGEN_API_NAME }}-integration"
ENV: "remote"
HOST: "internal-dev.api.service.nhs.uk"
BASE_URL: "https://int.api.service.nhs.uk/${{ vars.PROXYGEN_API_NAME }}"
ENV: "remote"
HOST: "int.api.service.nhs.uk"

Comment on lines +33 to +35
concurrency:
group: integration-environment
cancel-in-progress: true
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Does this block ensure that any currently running deployments are cancelled before this job starts?

- name: Sanitize branch name
id: branch
env:
RAW_BRANCH_NAME: "${{ github.head_ref }}"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is RAW_BRANCH_NAME required here? I guess currently this will always be integration anyway?

# ---------- Handle application with int ----------
- name: Create or update preview Lambda with int
env:
MOCK_URL: ${{ steps.names.outputs.int_url }}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think MOCK_URL here can be removed?

Comment on lines +124 to +125
MTLS_CERT="${API_MTLS_CERT:-/cds/pathology/int/mtls/client1-key-public}"
MTLS_KEY="${API_MTLS_KEY:-/cds/pathology/int/mtls/client1-key-secret}"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is mTLS required when accessing the INT APIM environment? Given we're including one with the Preview INT lambda I don't think there's any harm including it here but I guess we could potentially remove it form here and the preview-env INT deployment too?

prefix: coverage

# ---------- Test suites ----------
- name: "Run unit tests"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I don't think we need to run the tests included here and some of the will fail due to them relying on the mocks. We might want to develop some tests that run here (perhaps the acceptance tests for example), however for the moment I think we should be pretty confident that everything works functionally by the time we're creating a release.

@sonarqubecloud
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

Deployment Complete

@neil-sproston neil-sproston merged commit d2d8b54 into main Apr 20, 2026
39 checks passed
@neil-sproston neil-sproston deleted the CDAPI-119intWorkflow branch April 20, 2026 13:12
@neil-sproston neil-sproston restored the CDAPI-119intWorkflow branch April 20, 2026 13:13
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