mikehardy/buildcache-action

Allow config of all parts of buildcache

mikehardy opened this issue · 1 comments

Not sure how to do that, maybe offer a full copy of the JSON file or something - I'd like to not have to track the options from upstream - better to just allow a full passthrough behavior

came up with general design:

  • env vars and json are both effectively an "untyped API", I believe they are equivalent for purposes of configuration
  • the plugin is already using env vars effectively, so that seems like a reasonable criteria to decide which mechanism to use
  • therefore, the action will document respect existing env vars and publish them for future steps

Specifically

  • document that the env vars should be used for detailed config if wanted, with a pointer upstream
  • for any BUILDCACHE_ env vars in the environment, it will add them to GITHUB_ENV (so they may be co-located with the actual buildcache step for workflow file structural coherency)
  • respect any existing var definitions for the ones currently used (cache dir, log path, cache size, debug level etc)