Digital Ocean Playbook Improvements about browsertrix HOT 5 CLOSED

Some other things as part of this:

• Spaces bucket already exists
• Registry doesn't exist
• Restrict MongoDB access to cluster only
• MAYBE: restrict spaces access to cluster only
• Ensure kubectl config is configured through ansible for newly deployed clusters
• MAYBE: first run doctl auth from ansible
• Docs for env var name requirements
• Tear down playbook
• ansible-lint github action
• MAYBE: ansible tests for configuration drift, but this might be unnecessary because helm is primarily what manages 'deployments'

Combining all of these, my hope is that installing just ansible and running the playbook command listed in the documentation will lead to a working, secure DOMK deployment of Browsetrix

Potentially related issues / pulls:

• #772
• #778
• #313
• #777
• #566

from browsertrix.

MAYBE: restrict spaces access to cluster only

Hm, we sometimes share space across multiple buckets, and things default to private, so this might not be needed, or can just have a special key just for cluster.
Also, currently playbook assumes env variables are set already when running it - may be a better way?

from browsertrix.

Also, currently playbook assumes env variables are set already when running it - may be a better way?

Here I meant to document the env vars expected by the playbook. The playbook specifically looks for DO_API_KEY etc, while the DO docs specify setting the api key to TOKEN

Hm, we sometimes share space across multiple buckets, and things default to private, so this might not be needed, or can just have a special key just for cluster.

This makes sense. I wasn't sure originally, hence the maybe. Given this, I think it's not necessary.

from browsertrix.

Tracking all the PRs related to this DO playbook pass:

• #945
• #946
• #947
• #948
• #949
• #950
• #959
• #962
• #963
• #964

from browsertrix.

All the PRs been merged now 🎉

from browsertrix.