Revert "feat: consolidating staging into main and using main going fo…

.devcontainer/devcontainer.json

@@ -15,11 +15,11 @@
         "vscode": {
             "extensions": [
                 "hashicorp.terraform",
-                "charliermarsh.ruff"
+                "ms-python.black-formatter"
             ],
             "settings": {
                 "[python]": {
-                    "editor.defaultFormatter": "charliermarsh.ruff",
+                    "editor.defaultFormatter": "ms-python.black-formatter",
                     "editor.formatOnSave": true
                   }
             }

.gitignore

@@ -97,9 +97,6 @@ ENV/
 env.bak/
 venv.bak/
 
-# Local config / dev data
-config/local_inst_data.json
-
 # mkdocs documentation
 /site
 
@@ -117,6 +114,3 @@ dmypy.json
 # terraform
 **/.terraform/*
 **/terraform.tfvars
-
-# Cursor rule files
-.cursor/

.vscode/launch.json

@@ -29,21 +29,6 @@
       "env": {
         "ENV_FILE_PATH": "${workspaceFolder}/src/worker/.env"
       }
-    },
-    {
-      "name": "pytest (current file)",
-      "type": "debugpy",
-      "request": "launch",
-      "module": "pytest",
-      "args": [
-        "${file}",
-        "-v",
-        "-s"
-      ],
-      "cwd": "${workspaceFolder}",
-      "env": {
-        "ENV_FILE_PATH": "${workspaceFolder}/src/webapp/.env"
-      }
     }
   ],
 }

CONTRIBUTING.md

@@ -10,8 +10,8 @@ To get an overview of the project, please read the [README](README.md) and our [
 ## Getting started
 ### Creating Issues
 
-If you spot a problem, [search if an issue already exists](https://github.com/datakind/edvise-api/issues). If a related issue doesn't exist,
-you can open a new issue using a relevant [issue form](https://github.com/datakind/edvise-api/issues/new).
+If you spot a problem, [search if an issue already exists](https://github.com/datakind/sst-app-api/issues). If a related issue doesn't exist,
+you can open a new issue using a relevant [issue form](https://github.com/datakind/sst-app-api/issues/new).
 
 As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
 
@@ -28,7 +28,7 @@ poetry install --no-interaction
 As many other open source projects, we use the famous [gitflow](https://nvie.com/posts/a-successful-git-branching-model/) to manage our branches.
 
 Summary of our git branching model:
-- Get all the latest work from the upstream `datakind/edvise-api` repository
+- Get all the latest work from the upstream `datakind/sst-app-api` repository
   (`git checkout main`)
 - Create a new branch off with a descriptive name (for example:
   `feature/new-test-macro`, `bugfix/bug-when-uploading-results`). You can
@@ -107,7 +107,7 @@ You can type `pytest` to run your tests, no matter which type of test it is.
 
 ## Continuous Integration
 
-We use [GitHub Actions](https://github.com/datakind/edvise-api/actions)
+We use [GitHub Actions](https://github.com/datakind/sst-app-api/actions)
 for continuous integration.
 See [here](https://docs.github.com/en/actions) for GitHub's documentation.
 

README.md

@@ -2,14 +2,14 @@
 
 This repo contains:
 
-* [src/webapp/](https://github.com/datakind/edvise-api/tree/develop/src/webapp): The source code for the SST API (which is called by the SST frontend and by any direct API callers)
-* [src/worker/](https://github.com/datakind/edvise-api/tree/develop/src/worker): The source code for the SFTP Worker (which calls the SST API)
+* [src/webapp/](https://github.com/datakind/sst-app-api/tree/develop/src/webapp): The source code for the SST API (which is called by the SST frontend and by any direct API callers)
+* [src/worker/](https://github.com/datakind/sst-app-api/tree/develop/src/worker): The source code for the SFTP Worker (which calls the SST API)
 * [terraform/]
-(https://github.com/datakind/edvise-api/tree/develop/terraform): The Terraform configuration for the SST API/Frontend and other GCP resources including Cloud SQL setup, networking setup, secrets setup
+(https://github.com/datakind/sst-app-api/tree/develop/terraform): The Terraform configuration for the SST API/Frontend and other GCP resources including Cloud SQL setup, networking setup, secrets setup
 * .devcontainer/ and .vscode/: which allow easy setup if you are using VSCode as your IDE.
-* [devtools/](https://github.com/datakind/edvise-api/tree/develop/devtools): is a place to put utility scripts
-* .github/: contains mostly copied over files when this directory was forked from the student-success-tool repo, so likely much of it is outdated. The only Github action we've added is the [webapp-and-worker-precommit](https://github.com/datakind/edvise-api/blob/develop/.github/workflows/webapp-and-worker-precommit.yml) which is run on every push to develop. This action contains a python linter (we use [black](https://black.readthedocs.io/en/stable/)), and automated runs of the unit tests in the src/webapp/ and src/worker/ directories.
-* Additionally, [pyproject.toml](https://github.com/datakind/edvise-api/blob/develop/pyproject.toml) and [uv.lock](https://github.com/datakind/edvise-api/blob/develop/uv.lock) are important for dependency management. At time of writing, the worker is just skeleton code so there's no separate dependency management. In the long-term consider separating out the dependency management for the two programs. 
+* [devtools/](https://github.com/datakind/sst-app-api/tree/develop/devtools): is a place to put utility scripts
+* .github/: contains mostly copied over files when this directory was forked from the student-success-tool repo, so likely much of it is outdated. The only Github action we've added is the [webapp-and-worker-precommit](https://github.com/datakind/sst-app-api/blob/develop/.github/workflows/webapp-and-worker-precommit.yml) which is run on every push to develop. This action contains a python linter (we use [black](https://black.readthedocs.io/en/stable/)), and automated runs of the unit tests in the src/webapp/ and src/worker/ directories.
+* Additionally, [pyproject.toml](https://github.com/datakind/sst-app-api/blob/develop/pyproject.toml) and [uv.lock](https://github.com/datakind/sst-app-api/blob/develop/uv.lock) are important for dependency management. At time of writing, the worker is just skeleton code so there's no separate dependency management. In the long-term consider separating out the dependency management for the two programs. 
 
 
 NOTE: this repo was forked from the https://github.com/datakind/student-success-tool repo, which means some of the static files (e.g. CONTRIBUTING.md) may be outdated or may include irrelevant information from that repo. Please update those as you see fit. For information about the specific items listed above, defer to the specific readmes in the relevant directory.

SECURITY.md

@@ -8,4 +8,4 @@ If we verify a reported security vulnerability, our policy is:
 
 ## Reporting a Security Issue
 
-To report any security issues, please [raise an issue](https://github.com/datakind/edvise-api/issues/new/choose) and select **Security issue*
+To report any security issues, please [raise an issue](https://github.com/datakind/sst-app-api/issues/new/choose) and select **Security issue*

pyproject.toml

@@ -8,7 +8,7 @@ dependencies = [
     "databricks-sdk~=0.38.0",
     "pydantic~=2.10",
     "fastapi[standard]~=0.115.4",
-    "google-cloud-storage==2.19.0",
+    "google-cloud-storage~=2.18.2",
     "paramiko~=3.5.0",
     "cloud-sql-python-connector[pymysql]~=1.14.0",
     "sqlalchemy~=2.0.36",
@@ -26,16 +26,13 @@ dependencies = [
     "pandas~=2.0",
     "six~=1.16.0",
     "thefuzz[speedup]~=0.22.1",
-    "databricks-sql-connector[pyarrow]~=4.2.0",
+    "databricks-sql-connector~=3.5.0",
     "pandera~=0.13",
-    "mlflow~=2.22",
-    "cachetools",
-    "types-cachetools",
-    "edvise~=0.2.1",
+    "mlflow~=2.15.0"
 ]
 
 [project.urls]
-Repository = "https://github.com/datakind/edvise-api"
+Repository = "https://github.com/datakind/sst-app-api"
 
 [dependency-groups]
 dev = [
@@ -53,15 +50,9 @@ dev = [
 requires = ["hatchling"]
 build-backend = "hatchling.build"
 
-[tool.hatch.metadata]
-allow-direct-references = true
-
 [tool.uv]
 default-groups = ["dev"]
 
-[tool.uv.sources]
-edvise = { git = "https://github.com/datakind/edvise.git", rev = "develop" }
-
 [tool.ruff]
 line-length = 88
 indent-width = 4
@@ -93,11 +84,8 @@ lines-after-imports = 1
 [tool.pytest.ini_options]
 minversion = "8.0"
 addopts = ["--verbose", "--import-mode=importlib"]
-filterwarnings = [
-    "ignore::DeprecationWarning",
-    "ignore::FutureWarning:pandera",
-]
-testpaths = ["src"]
+filterwarnings = ["ignore::DeprecationWarning"]
+testpaths = ["tests"]
 
 [tool.mypy]
 files = ["src"]

src/webapp/Dockerfile

@@ -13,11 +13,6 @@ WORKDIR /app
 # Add project files
 ADD uv.lock pyproject.toml /app/
 
-# Install git and ca-certificates
-RUN apt-get update \
-  && apt-get install -y --no-install-recommends git ca-certificates \
-  && rm -rf /var/lib/apt/lists/*
-
 # Install dependencies
 RUN uv sync --frozen --no-install-project
 

src/webapp/README.md

@@ -51,7 +51,7 @@ In the long-term, look into a way to have the API key --> token conversion be ha
 
 ## Databases
 
-All data is stored in MySQL databases for dev/staging/prod, these are databases in GCP's Cloud SQL. In the local environment, the database is sqlite. The main file you'll want to look at for database table definitions is [src/webapp/database.py](https://github.com/datakind/edvise-api/blob/develop/src/webapp/database.py).
+All data is stored in MySQL databases for dev/staging/prod, these are databases in GCP's Cloud SQL. In the local environment, the database is sqlite. The main file you'll want to look at for database table definitions is [src/webapp/database.py](https://github.com/datakind/sst-app-api/blob/develop/src/webapp/database.py).
 
 At time of writing, the databases the API cares about and tracks, are as follows:
 
@@ -112,7 +112,7 @@ Enter into the root directory of the repo.
 
 You're now in your virtual env with all your dependencies added.
 
-For all of the following, the steps above are pre-requisites and you should be in the root folder of `edvise-api/`.
+For all of the following, the steps above are pre-requisites and you should be in the root folder of `sst-app-api/`.
 
 ### Spin up the app locally:
 
@@ -168,25 +168,3 @@ The process to upload a file involves three API calls:
 ## Local VSCode Debugging
 
 From the Run & Debug panel (⇧⌘D on 🍎) you can run the [debug launch config](../../.vscode/launch.json) for the webapp or worker modules. This will allow you to set breakpoints within the source code while the applications are running.
-
-## Local edvise development override
-
-Production uses a pinned Git reference for `edvise`. For local development, use an
-editable install after syncing the environment.
-
-1. Clone `edvise` alongside `edvise-api` (so `../edvise` exists).
-2. Run `uv sync`.
-3. Override locally: `uv pip install -e ../edvise`
-
-To revert back to the pinned Git dependency, run `uv sync --reinstall-package edvise`.
-
-## Local institutions (optional)
-
-You can seed the local database with institution, batch, and file metadata that matches dev or staging (names, UUIDs, batch membership) without checking secrets into Git.
-
-1. Copy `config/local_inst_data.example.json` to `config/local_inst_data.json`. The latter is gitignored.
-2. Edit `local_inst_data.json` to match your needs. Use the example file as the schema: one array element per institution, with `inst_id`, `name`, and optionally `state`, `pdp_id`, `batches`, and `files`.
-
-If the file is missing, startup skips this step and the default local seed in code still applies.
-
-**Limitation:** Endpoints that read uploaded CSV (for example EDA) load blobs from GCS under the bucket name `dev_<institution_uuid_hex>`, not from this JSON. To exercise those flows locally you still need GCP credentials and the corresponding objects in that bucket, or you rely on tests/mocks instead.

src/webapp/config.py

@@ -51,7 +51,6 @@
     "DATABRICKS_HOST_URL": "",
     # The service account that is used in Databricks to access GCP buckets.
     "DATABRICKS_SERVICE_ACCOUNT_EMAIL": "",
-    "GCP_CACHE_BUCKET": "",
 }