Support get manifest from local

[retzero]

Description:
We ran into a rate limit issue while running our GitHub Enterprise Server instance.
There are several topics discussed below, but they are not suitable for us.
#219, #427, #316

The rate limit problem seems to be caused by importing the manifest file located on github.com.
Wouldn't the problem go away if the action import a local manifest file instead?

I suggest using a local file instead of calling the api to github.com if the hosted runner has a specific environment variable (eg, SETUP_PYTHON_MANIFEST_FILE_LOCATION).

https://github.com/actions/setup-python/blob/main/src/install-python.ts#L19

+ # pseudo code
+ if (SETUP_PYTHON_MANIFEST_FILE_LOCATION is set) {
+   const manifest: tc.IToolRelease[] = getManifestFromLocal(
+   ...
+ } else {
  const manifest: tc.IToolRelease[] = await tc.getManifestFromRepo(

Justification:
Justification or a use case for your proposal.

Are you willing to submit a PR?

[IvanZosimov]

Hi, @retzero 👋 ! Thank you for this feature request! Unfortunately we aren't planning to implement this feature, but probably I can help you with the issue itself. What is your current rate limit? (check this info about getting your rate limit)

[retzero]

@IvanZosimov

Thank you for the feedback. I'm looking for a more efficient way to solve the rate limit problem. This is our situation.

• Our company do not allow enabling GitHub Connect for some reasons.
• We have tens of thousands of build requests per day.
• And we're operating 500+ self-hosted runners.
• There is only one IP exposed to the outside due to the company's NAT configuration.
• We want to avoid including GitHub.com's PAT in our development source code.
• Currently, we're using self hosted runners w/ python tool cache set as guided here.
  • Hundreds of developers demand different python versions, so we have to caching tens of GB of full stable versions.
  • It is expensive(time-consuming) to use ephemeral options and/or re-initialize the toolcache where changes occur in every build.

[IvanZosimov]

Hi, @retzero, thanks for clarifying your case. Unfortunately, I think the best way to solve your problem is to fork action as was suggested here and apply the changes you need.

[brcrista]

Duplicate of #229

[brcrista]

We want to avoid including GitHub.com's PAT in our development source code.

Definitely don't put it in your source code. You would store it as a secret in your repo.