Skip to content

chore: deploy workspace proxies on fly.io #10983

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

Merged
merged 14 commits into from
Dec 4, 2023
Merged

chore: deploy workspace proxies on fly.io #10983

merged 14 commits into from
Dec 4, 2023

Conversation

matifali
Copy link
Member

@matifali matifali commented Dec 1, 2023

This pull request adds a new job called deploy-wsproxies thst is responsible for deploying the workspace proxies to the fly.io platform. The deployment is triggered only when the pull request is made from the main branch.

The deploy-wsproxies job updates our workspaces proxies in 3 fly.io regions

  1. Paris
  2. Sydney
  3. Sao Paulo

This pull request ensures that the proxies are up-to-date with main btanch.

@matifali matifali requested a review from deansheather December 1, 2023 10:24
@matifali matifali requested a review from johnstcn December 1, 2023 10:25
@matifali matifali changed the title Add deployment of fly.io workspace proxies chore: deploy workspace proxies on fly.io Dec 1, 2023
@matifali matifali requested a review from deansheather December 3, 2023 21:39
Comment on lines +804 to +806
TOKEN_PARIS: ${{ secrets.FLY_PARIS_CODER_PROXY_SESSION_TOKEN }}
TOKEN_SYDNEY: ${{ secrets.FLY_SYDNEY_CODER_PROXY_SESSION_TOKEN }}
TOKEN_SAO_PAULO: ${{ secrets.FLY_SAO_PAULO_CODER_PROXY_SESSION_TOKEN }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fly.io doesn't have a way of adding secrets in their dashboard?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They do have but I prefer we store all secrets in GitHub Actions. I can move if you disagree.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use --env on the flyctl command does it store the secrets in plain text visible on the fly.io dashboard? If so then we should probably move them to secrets on fly.io instead of GH

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fly.io has no environment section on the dashboard, so they do not appear anywhere.

Copy link
Member

@deansheather deansheather left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

meant to approve that, please see comments above

Co-authored-by: Dean Sheather <dean@deansheather.com>
@matifali matifali merged commit b212bd4 into main Dec 4, 2023
@matifali matifali deleted the fly-wsproxy branch December 4, 2023 09:12
@github-actions github-actions bot locked and limited conversation to collaborators Dec 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants