The examples and tests now read the resource key from the aligned 51DEGREES_RESOURCE_KEY environment variable first, with the legacy names still supported. See #92.
The CI workflows in this repository map the GitHub secret SUPER_RESOURCE_KEY into the build. To complete the alignment the secret name should change as well. GitHub secret names must not start with a digit, so the secret cannot be called 51DEGREES_RESOURCE_KEY itself. The closest valid name is _51DEGREES_RESOURCE_KEY, using the permitted leading underscore.
Recommended steps:
- Create an organisation secret named
_51DEGREES_RESOURCE_KEY with the same value as SUPER_RESOURCE_KEY.
- Update the workflow mappings in this repository to read
secrets._51DEGREES_RESOURCE_KEY where they currently read secrets.SUPER_RESOURCE_KEY.
- Remove the legacy
SUPER_RESOURCE_KEY secret once no repository references it.
The workflows pass the value onwards as the TestResourceKey parameter, so the rename is contained to the workflow files and the organisation secret store.
The examples and tests now read the resource key from the aligned
51DEGREES_RESOURCE_KEYenvironment variable first, with the legacy names still supported. See #92.The CI workflows in this repository map the GitHub secret
SUPER_RESOURCE_KEYinto the build. To complete the alignment the secret name should change as well. GitHub secret names must not start with a digit, so the secret cannot be called51DEGREES_RESOURCE_KEYitself. The closest valid name is_51DEGREES_RESOURCE_KEY, using the permitted leading underscore.Recommended steps:
_51DEGREES_RESOURCE_KEYwith the same value asSUPER_RESOURCE_KEY.secrets._51DEGREES_RESOURCE_KEYwhere they currently readsecrets.SUPER_RESOURCE_KEY.SUPER_RESOURCE_KEYsecret once no repository references it.The workflows pass the value onwards as the
TestResourceKeyparameter, so the rename is contained to the workflow files and the organisation secret store.