It does with some hoops IIRC. I used act a couple of years ago to test a very distributed flow for enterprise IaC projects. I can’t remember all of the things we had to do and I think I’m conflating some of the podman issues we had on macOS with act issues. AWS credentials were an annoyance, I think, but we worked around it with some community code. Our primary purpose for act was to be the local testing for enterprise action deployment so I’d guess it’s close to yours. I think our conclusion was to distribute the actions to each repo rather than use the central .github repo for actions because of how GitHub handles overrides. My memory is really fuzzy.
If you’re going to believe this internet stranger, start with a very simple set of demos to vet me. I remember being very happy; I do not remember how the team solved it. M
Totally agree. I’m glad you read between the lines there. It’s out there if you have the resources to throw at it.
Like most DevOps things, it’s all about the opinionated ecosystem you hop in. It has most things and does most of the stuff you want until you decide to adapt the pattern to your use case and holy fucking shit is it hard to adapt opinionated ecosystems. That’s why I continue to have jobs.