Support private plugin repositories

[gewenyu99]

Originally posted on Canny by Tyler Jang:

Support private repositories through a GITHUB_TOKEN, gh client, git credential manager, or built-in Trunk auth flow.

Private GitHub plugin repositories are not currently supported: https://docs.trunk.io/check/advanced-setup/plugins#plugins-scope

[sheldonhull]

I got notified of this option from @TylerJang27 which I appreciate being in beta.
I'll do my best to give it a try and report back progress 🙇🏻

[sheldonhull]

I'm using private azure devops repo.
If you are using the upstream api to query tags then that would explain it if it's not being cloned or done in a generic git way.

I did succeed after a few hours of work with azure devops but no ability out of the box to tell a team downstream trunk upgrade to pull in the changes. I'd have to give them a script or push those out myself since the upgrade won't honor that.

Thanks for the help today 👍🏻

[sheldonhull]

@TylerJang27 I guess I could probably create an azure cli call to fetch upstream latest tag and essentially reproduce the effect myself using azure cli call+ yq as tools.

Refresh me though if I've got folks on windows and Mac will an action script run in an emulated shell or whatever the user is running trunk in? Therefore I'd have to have it fall a cross platform PowerShell script or use another language runtime like Go and include a main.go to run as a custom action in my plugins?

[TylerJang27]

To clarify, you're trying to write a custom Trunk Action that mimics the behavior of fetching latest and updating the plugin ref? Trunk Actions run in a managed bash by default, but you can override that with actions.definitions[].shell

[sheldonhull]

Yes. So is that managed bash cross platform. I know of the go package that has a shell that's cross platform but limited tooling in it like mkdir and awk aren't accessible.

Any details on docs on this managed bash so I can write some scripts that work on windows and Linux/mac?

[TylerJang27]

Sorry, I misspoke slightly. On Linux/Mac we'll inherit from your PATH and use the bash we find there (and whatever commands you call). On Windows we install from git-bash and also inherit your PATH.

You can get some additional debug info about what we run using trunk actions history <action-id> and looking at the YAML files. You can also set actions.output_level: verbose for some info as things execute