Adding and removing operators

Find the numeric id

curl -s https://api.github.com/users/<github login> | python3 -c 'import json,sys; print(json.load(sys.stdin)["id"])'

Add an operator

1. Add the id to sa_operator_github_ids in infra/ansible/inventories/<env>/group_vars/all.yml, for example sa_operator_github_ids: "<id 1>,<id 2>", and commit it with a line in the change description saying who and why.
2. Converge the core nodes so the control plane gets the new list:
   make staging-deploy SA_IMAGE_TAG=<current release> SA_RELEASE_MANIFEST=<release-images.json>
   
   The core compose file changes (OPERATOR_GITHUB_IDS), so controlplane is recreated on both core nodes. At start it syncs the flag for every user; each changed user gets an audit row user.operator_sync (actor system:startup).
3. The person signs in to https://app.<input I4>/. The operator area appears in the console. If they had never signed in before, their user row is created at that sign-in with the flag set.

Remove an operator

1. Remove the id from sa_operator_github_ids, commit, and converge as above.
2. When the control plane restarts, it sets is_operator = false for that user and writes user.operator_sync. From then on every operator route answers 403 operator_required for them, even with a session that is still open.
3. Revoke the operator API keys that person created, unless another operator takes them over knowingly (operator-key-revocation.md). To list them, on the database leader:
   select k.id, k.name, k.prefix, k.created_at, k.expires_at, k.revoked_at
   from cp.operator_api_keys k join cp.users u on u.id = k.created_by
   where u.github_id = <github id>;
   
4. If the removal is because the account may be compromised, also end that person’s console sessions at once:
   delete from cp.sessions where user_id = (select id from cp.users where github_id = <github id>);
   
   and follow security-incident.md.

Exercised