feat: private feed deployment#5556
Draft
michaelkedar 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.
Merge (& apply) after #5536 is merged/applied.
Set up the ingestion pipeline for a private vuln feed proof of concept.
For ease, I've added this as a stage after the production deployment (which does mean we can only promote prod releases to the private pipeline).
Modified many services to accept the pub/sub topics/subscriptions and datastore ID as environment variables, so that we can maintain the separation.
I can't seem to find a way to make the backup job work as-is to target the non-
(default)database, so I've excluded it for now. Might need to rewrite it to use the firestore API instead.