Skip to content

eli-731 adding missing permissions that the regression test role needs#658

Merged
eddalmond1 merged 1 commit intomainfrom
feature/eja-eli-731-finessing-regression-test-role-permissions
Apr 27, 2026
Merged

eli-731 adding missing permissions that the regression test role needs#658
eddalmond1 merged 1 commit intomainfrom
feature/eja-eli-731-finessing-regression-test-role-permissions

Conversation

@eddalmond1
Copy link
Copy Markdown
Collaborator

@eddalmond1 eddalmond1 commented Apr 27, 2026

Description

Adding additional permissions needed for the regression test role

Context

So that tests can run automatically

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

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.

@eddalmond1 eddalmond1 requested a review from a team as a code owner April 27, 2026 11:53
"secretsmanager:DescribeSecret"
]
"secretsmanager:DescribeSecret",
"secretsmanager:UpdateSecretVersionStage",
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

UpdateSecretVersionStage and PutSecretValue are used by the regression tests to test hashing/secrets

"dynamodb:Scan",
"dynamodb:UpdateItem",
"dynamodb:DeleteItem",
"dynamodb:BatchWriteItem",
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Regression tests use BatchWrite to write test data

variable = "token.actions.githubusercontent.com:job_workflow_ref"
values = [
"${var.github_org}/${var.regression_repo}/.github/workflows/regression_tests.yml@*"
"repo:${var.github_org}/${var.regression_repo}:*",
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

We need to allow the role to be assumed by workflows in both the main repo (this one) and the regression test repo

Copy link
Copy Markdown
Contributor

@ayeshalshukri1-nhs ayeshalshukri1-nhs left a comment

Choose a reason for hiding this comment

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

LGTM !

# Environment-specific actions
dynamic "statement" {
for_each = var.environment == "preprod" ? [1] : []
for_each = contains(["dev", "test", "preprod"], var.environment) ? [1] : []
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

We need dynamoDB permissions for the regression test role to be within the permissions boundary for all pre-live environments

@eddalmond1 eddalmond1 merged commit 5103c61 into main Apr 27, 2026
26 checks passed
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