DINO-1050: remove git crypt stuff

.gitignore

@@ -53,7 +53,18 @@ node_modules
 /.kotlin/
 
 .env
-!.env.**.example
+
+# Local secrets.
+.env.shared
+.env.ci
+.env.ci-app
+.env.staging
+.env.production
+.env.production-ro
+.env.migrator
+infra/.env.production
+internal/.env.ci
+internal/standup-bot/.env.production
 
 # Ignore the static folder, it will be generated in the build process for production use.
 **/static/*

README.md

@@ -76,8 +76,7 @@ This repository is a monorepo that contains many different pieces of Codebloom,
 - Our internal tools (e.g. custom Ink CLI scripts & our internal standup bot) are currently being written in [Rust](https://rust-lang.org/) and [TypeScript](https://typescriptlang.org)
   - [Goto `internal/`](./internal/)
   - [View detailed documentation](./internal/README.md)
-- Our secrets across all environments which are decryped with [git-crypt](https://github.com/AGWA/git-crypt).
-  - [Goto `example.env`](./example.env)
+- Environment secrets live in local env files generated from Azure.
   - [View detailed documentation](./docs/local/SECRET.md)
 
 ## Setup

docs/local/SECRET.md

@@ -1,49 +1,19 @@
-# Prerequisites
+# Secrets
 
-Please ensure that you install the following (homebrew is a recommendation but not a requirement):
+Local environment files come from Azure. Git does not store them.
 
-1. Install `gpg`
+[Setup](./SETUP.md) covers the rest of local setup.
 
-```bash
-brew install gpg
-```
+These files stay on your machine:
 
-1. Install `git-crypt`
-
-```bash
-brew install git-crypt
-```
-
-# New Codebloom Developer (needs access)
-
-If you don't have access to environment secrets yet, you need to generate a public GPG key and add it to your GitHub profile. If you know what you are doing, you can choose to do so manually. Else, Codebloom has a script you can run to do it for you instead. Please run:
-
-```
-just git-crypt-generate-key
-```
-
-After getting access,
-from your main branch:
-run:
-
-```
-git pull
-```
-
-then run:
-
-```
-git-crypt unlock
-```
-
-and follow the instructions inside the script.
-
-# Existing Codebloom Developer (has access)
-
-Once the new developer has generated a key, please run:
-
-```
-just git-crypt-add-user
-```
-
-and follow the instructions inside the script.
+- `.env`
+- `.env.shared`
+- `.env.ci`
+- `.env.ci-app`
+- `.env.staging`
+- `.env.production`
+- `.env.production-ro`
+- `.env.migrator`
+- `infra/.env.production`
+- `internal/.env.ci`
+- `internal/standup-bot/.env.production`

docs/local/SETUP.md

@@ -196,7 +196,6 @@ You can feel free to use any viewer you want, but we would recommend [DataGrip](
 
 # Secrets
 
-You can speed up the setup process by making a copy of `.env.example` to `.env`.
-You will also find explanations and documentation about how to source the value for each key.
+Local `.env` comes from Azure.
 
 If there is a key specific to an environment (such as `CI` or `staging` environment), please consult the tech docs within the `CI` group.

internal/standup-bot/README.md

@@ -9,10 +9,8 @@ Codebloom Standup Bot is an internal application written in [Rust](https://rust-
 
 ### Run
 
-1. Create `.env`
-1. Copy everything from `example.env` to `.env`
-1. Fill out your `.env` file
-1. Simply run `cargo run` to compile & run the binary.
+1. Put the Azure-generated `.env` in this directory.
+1. Run `cargo run` to compile and run the binary.
 
 `DISCORD_ROLE_ID` is required and must be an unsigned 64-bit integer. It selects
 the role mentioned in standup messages and the members eligible for end-of-day