uranusjr commented on issue #14989:
URL: https://github.com/apache/airflow/issues/14989#issuecomment-808267669
Using GitHub Action’s cache sounds like a cool idea. The only concern I have
is the cache can be pretty difficult to purge if something goes wrong (maybe
just me not knowing a good way to do it). Maybe we should have a “cache
busting” part to the key (e.g. `cache-inventory-${{
hashFiles('constrant-3.8.txt') }}-${{ cacheKey }}` where `cacheKey` is a
variable in the Action’s config) so we can force a cache miss when we need to.
Generally constraints (and requirements) file syntax is considered pip
internals, but the files in this case are entirely managed by Airflow anyway,
so that’s not really a concern.
We’ll probably need check if each third-party has a versioned documentation
as well (not a given). And if one doesn’t, just default to `latest`?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
