-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Please create a new 1P vault called Mobile-Deploy-CI-Test #56493
Comments
Triggered auto assignment to @robertjchen ( |
@roryabraham done, let me know if you can see it 👍 |
Nice, yes I see it thanks |
@robertjchen can you please:
Thanks! (I attempted this but got a 403 trying to create the service account) |
@robertjchen Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
bobby's OOO this week, reassigning |
Triggered auto assignment to @fukawi2 ( |
Looks like robert did it but didn't save it in the vault, i rolled the token and saved the new version in the vault |
@coleaeason can you please go to https://github.com/Expensify/App/settings/variables/actions and add |
done |
Problem
We are working on setting up https://github.com/Expensify/App-Test-Fork for full dry-run e2e tests of the NewDot deploy cycle, with little to no permanent code diff between the fork and the upstream.
To access secrets in NewDot CI/CD, we use 1P. We want a separate test vault so that we can set up all our dummy credentials without risking accidentally using production secrets.
Solution
Please set up a new 1P vault called Mobile-Deploy-CI-Test. ring access level can match Mobile-Deploy-CI vault
The text was updated successfully, but these errors were encountered: