You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a TRE Administrator
I want to use GitHub environment variables instead of secrets to store non-sensitive data
So that it's easier to review the configuration of a repo.
I think this list of secrets should be turned into variables instead:
TRE_ID
LOCATION
MGMT_RESOURCE_GROUP_NAME
MGMT_STORAGE_ACCOUNT_NAME
ACR_NAME
CORE_ADDRESS_SPACE
TRE_ADDRESS_SPACE
TERRAFORM_STATE_CONTAINER_NAME
CORE_APP_SERVICE_PLAN_SKU
WORKSPACE_APP_SERVICE_PLAN_SKU
RESOURCE_PROCESSOR_NUMBER_PROCESSES_PER_INSTANCE
ENABLE_SWAGGER
Acceptance criteria
CI/CD GitHub Actions (yml) updated to use variables instead of secrets
Instructions updated
The text was updated successfully, but these errors were encountered:
Description
As a TRE Administrator
I want to use GitHub environment variables instead of secrets to store non-sensitive data
So that it's easier to review the configuration of a repo.
I think this list of secrets should be turned into variables instead:
Acceptance criteria
The text was updated successfully, but these errors were encountered: