Add CrdtMerge deployment for k8s and GHA #1171
Draft
Conversation
This file contains 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
UI unit Tests12 tests 12 ✅ 0s ⏱️ Results for commit 3bbce76. |
|
If you end up not making a copy of develop-api.yaml and you want to filter based on paths changed you can use this action |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #1163.
This adds a new k8s deployment for CrdtMerge (in its own pod), and adds GHA workflow steps to build and deploy it just like our other pods.
New secret named
crdtmergeshould be created in staging and prod environments, containing the username and password of a user that will be allowed to Send/Receive any project. For local development this should just be"admin"and"pass", but for staging and production we'll want a dedicated CrdtMerge user, so that if CrdtMerge credentials leak we can revoke that user's access and then set up a new one.