* Rename docker secrets and parameterize docker user
* Apply suggestions from code review
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
* Adds valid PAT testing to existing ec2 pipes
adds the same workflow seen in gradle.yml to other pipelines
* Reorder PAT selection
rename SELF_RUNNER_GITHUB_ACCESS_TOKEN_1 ->
DAVINCHIA_PAT
remove LABEL_BOT_USERNAME
* Use shell hacks to find valid PAT
if rate limit exceeded try another key
* Use tim's version of the ec2 runner
this is a weird solution with weird limitations. should address the short term pain (march 2022)
* Adds tim's ocotocat rate limiter
* Change all the actions to our homebrew ec2 fork
* Compiles the dist in npm
* Update action to v15.0.1
* Update to v15.0.2
* Update to v15.0.3
* Update to v15.0.4
Co-authored-by: Tim Roes <tim@airbyte.io>
This enables all slash commands to also work on PRs created from forks. This will not run CI on PRs coming from a fork. There are unfortunately some limitations around injecting secrets in pull_request actions, which I described in detail in this comment.
I've done most of the testing for this in https://github.com/timroes/github-actions-test to test out that the context are set the way I'd expect them.
There's one risk: if any of the actual build scripts called by one of the slash commands would use this repository hard-coded they might fail. I've tried to search through the whole code base and don't believe this is the case.
* feat: add publish-external command to slash commands to publish external connector images
* fix: publish only stpec to cache
* fix: according to new script changes
* fix: removed tox installation
* fix: version is not read from command
