Dave Stanke
Dave Stanke
The status badges in README.md that point to ci.bazel.io are currently pointing to dead links. Can we update those? Here's the page for that build: https://ci.bazel.io/job/rules_closure/
On the page: https://cloud-ops-sandbox.dev/docs/user-guide/learn-cloud-operations/cloud_slo_monitoring/ the image links are broken:
Currently, the setup instructions store TF state locally on the user's local machine. Let's provide some instructions on how to use a remote state (e.g. gcs), which is better for...
I think we lost these instructions when we updated the README(?): https://github.com/dora-team/fourkeys/blob/main/setup/deprecated/README.md#integrating-with-a-live-repo
After #416 is complete, let's move a basic version of setup instructions onto the main README. Any advanced setup info can be put in `/docs`
Let's move a lot of the details from /README.md into a /docs/ folder.
There's a build config specifically for the parsers (`bq-workers/parsers.cloudbuild.yaml`), which the terraform installer instructions reference. But the e2e test doesn't use this; it just build the containers directly. Let's rework...
Hey @rogerthatdev -- in `/terraform/example/variables.tf`, I see reference to a map variable called `parser_container_urls`. But as far as I can tell, that variable isn't actually used. Instead, each of the...
(#298 seems abandoned but we should still do it.) GitHub [now sends SHA256-encrypted webhooks](https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks#validating-payloads-from-github) ... let's validate those and sunset the SHA1 validation.
As our user base grows, and we continue to make improvements, the use case of updating an existing installation will become increasingly important. Let's add an e2e test that keeps...