Skip to content

Conversation

@gusfcarvalho
Copy link
Contributor

This introduces the option to authenticate leveraging a github app as opposed to a github token. This approach tends to be better seen for organizations as app policies are somewhat better to govern - and all github tokens themselves become very short lived.

Signed-off-by: Gustavo Carvalho <gustavo@externalsecrets.com>
@gusfcarvalho
Copy link
Contributor Author

gusfcarvalho commented Sep 25, 2025

@jonathandavies-CS @ssherar what would be the best way to test these changes are working? Is there any suite I can run ? 😄

@ssherar
Copy link
Contributor

ssherar commented Sep 26, 2025

hey @gusfcarvalho

Thanks for the PR - it was on our to-do list to add app authentication instead of PATs 🎉

Unfortunately there is no test suites written for many of the API driven plugins (as the plugin eco-system matures it is becoming a priority to write them!). However the best approach is to build and configure the agent (https://github.com/compliance-framework/agent) and configure the app with the permissions in the README.md and check if the exit code is 0.

You might need a http sink for the evidence creation if you don't want to spin up the API (but it's pretty simple to run in docker-compose, check https://github.com/compliance-framework/demo)

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