github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 10:18:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Make process clearer around access approval (#5167)

Browse Source 
Minor rewording of the process to request access to staging / prod.

Signed-off-by: Jamil <jamilbk@users.noreply.github.com>
This commit is contained in:
Jamil
2024-05-31 10:07:18 -07:00
committed by GitHub
parent b64900b513
commit d921c07876
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
elixir/README.md
View File

@@ -281,9 +281,13 @@ to the acceptance test that you are running.
## Connecting to a staging or production instances
We use Google Cloud Platform for all our staging and production infrastructure.
You'll need access to this env to perform the commands below; to get and access
you need to add yourself to `project_owners` in `main.tf` for each of the
[environments](../terraform/environments).
You'll need access to this env to perform the commands below; to request access
you need to complete the following process:
- Open a PR adding yourself to `project_owners` in `main.tf` for each of the
[environments](../terraform/environments) you need access.
- Request a review from an existing project owner.
- Once approved, merge the PR and verify access by continuing with one of the steps below.
This is a danger zone so first of all, ALWAYS make sure on which environment
your code is running: