-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add artifact_proxy
server
#222
Conversation
artifact_proxy
server
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, switching to my other account.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I can't approve since this was my PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@@ -0,0 +1,62 @@ | |||
name: Deploy Artifacts Proxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It scares me ever so slightly that we're hosting this in our public repo. Any commit reviewed to artifacts_proxy could end up directly in prod... Which I guess is good? Just a bit scary to have it so little interaction to get to prod.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we can make this a manual trigger only if you prefer. Ideally we make the CI checks as robust as we need to give us the confidence to deploy automatically 😄
This is still in-development, but enough to check in for now.