Deploy application via GitHub Actions#319
Draft
confused-Techie wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In an effort to reduce bus factor, and manual actions on my part, I hope to finally take the time needed to manage automated deployments for this repository.
Now, you'll notice it's only semi manual, I thought it'd be best to enforce a manual human to actually deploy this code, but by making it a workflow we can ensure anyone with proper access to this repository can deploy to GCP as needed.
The first big step, is figuring out how to deploy the main API, which is the work I have currently, all that's left is to manage the authentication flow, but luckily GCP tries to make it pretty easy. The second step here is figuring out how to write all the secret files to disk that we need to safely, which I believe I've managed to do.
Beyond this, there's still more to figure out:
./docs/resources/featured_packages.json,./docs/resources/featured_themes.json,./docs/resources/name_ban_list.json./dispatch.yamlWhile I'd love to figure all of those out, it seems to me that the API itself is the most common new deployment, and the thing most likely to need change that could all be done by someone without further access.