Skip to content

CCM-15541: Gateway Cluster Deployment#222

Draft
jamesthompson26-nhs wants to merge 6 commits intomainfrom
feature/CCM-15541_Gateway_Cluster_Deployment
Draft

CCM-15541: Gateway Cluster Deployment#222
jamesthompson26-nhs wants to merge 6 commits intomainfrom
feature/CCM-15541_Gateway_Cluster_Deployment

Conversation

@jamesthompson26-nhs
Copy link
Copy Markdown
Contributor

@jamesthompson26-nhs jamesthompson26-nhs commented Mar 23, 2026

Description

  • Removes the original ASG and related resources.
  • Removes several unused SSM params which were originally intended to support automated deployments via service principal.
  • Brings dev/nonprod in line with production gateway config for testing purposes.
  • Tidy up the powershell script in the user-data to remove version pinning of the gateway software(which doesn't work anyway with the on premises gateway).
  • Moves the Athena ODBC driver download URL to a variable. Using a URL like this has a smell - open to alternatives for self-hosting it maybe?

Context

Required preparation to migrate off the incorrectly deployed Production instance.

My proposal is we should set up the 2 new standalone instances as NEW Gateway cluster in the PowerBI service and migrate the reports to use this and then remove the existing cluster and underlying un-managed instance.

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 am familiar with the contributing guidelines
  • 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
  • If I have used the 'skip-trivy-package' label I have done so responsibly and in the knowledge that this is being fixed as part of a separate ticket/PR.

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.

@jamesthompson26-nhs jamesthompson26-nhs requested review from a team as code owners March 23, 2026 10:59
@jamesthompson26-nhs jamesthompson26-nhs changed the title Feature/ccm 15541 gateway cluster deployment CCM-15541: Gateway Cluster Deployment Mar 23, 2026
@jamesthompson26-nhs jamesthompson26-nhs marked this pull request as draft March 23, 2026 11:05
@jamesthompson26-nhs jamesthompson26-nhs force-pushed the feature/CCM-15541_Gateway_Cluster_Deployment branch from 0a6706e to 056d713 Compare April 8, 2026 11:53
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 8, 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.

2 participants