Closed kikito closed 2 years ago
@wheelerlaw I rebased this PR after merging the CI changes, yet it fails again with the same errors. Any ideas?
merged this fix; https://github.com/Kong/kong-license/pull/19 so now the CI fails properly on the license failure. But still, that should not happen, seems something is still wrong with the secret.
I reran another repo, using the same license action, that one succeeded properly.
Forks of public repositories do not have access to secrets, according to GH's documentation:
Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's GitHub Actions workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes.
So this PR will need to be reopened from the branch inside this repository. I tested this here.
This PR encrypts the key field if the keychain feature (an EE-exclusive feature at the moment) is present.