-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Create a basic AGENTS.md file for LLMS #160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,100 @@ | ||
| # LLM Context Guide for Analytics Data Platform | ||
|
|
||
| This repository contains ELT code for an Iceberg-based data warehouse, together with | ||
| infrastructure code used to run the warehouse both locally (docker-compose) and in an | ||
| OpenStack cloud (Ansible). | ||
|
|
||
| Use this document as a concise, developer-friendly reference when working with the | ||
| repository or providing context to an assistant/agent about the project structure and | ||
| common developer tasks. | ||
|
|
||
| ## Purpose | ||
|
|
||
| - Give human developers and LLM-based agents the essential repository layout and | ||
| pointers for local development, testing and deployment. | ||
| - Point to the configuration locations used for certificates, local environments, | ||
| and deployable Ansible playbooks/roles. | ||
|
|
||
| ## Repository layout (high level) | ||
|
|
||
| ```text | ||
| . | ||
| ├── certs/ # Certificate request configurations used for HTTPS/SSL | ||
| ├── elt-common/ # Reusable Python package with common ETL/ELT helpers used by the warehouses | ||
| ├── docs/ # User and developer documentation using MkDocs. See `docs/src` for content used in the published docs site. | ||
| ├── infra/ | ||
| │ ├── ansible-docker/ # Ansible playbooks/roles to deploy the system to the STFC (OpenStack) cloud. | ||
| │ └── local/ # docker-compose configuration for a local development environment and end-to-end CI tests. | ||
| └── warehouses/ # One subdirectory per (Lakekeeper) warehouse. Each contains ELT code to extract, transform and load data from external sources into Iceberg tables. | ||
| ``` | ||
|
|
||
| ## Pre-commit hooks | ||
|
|
||
| - Static code checks are enforced using `prek`. Install with your environment's tooling and run checks | ||
| on all files with `prek run --all-files`. Install the pre-commit hook with `prek install`. | ||
|
|
||
| ## Running tests | ||
|
|
||
| - There are both unit and e2e tests for the `elt-common` package under `elt-common/tests/`. They are | ||
| written using `pytest`. | ||
| - Install the package in editable mode + dev dependencies in a Python environment, e.g. with `uv` | ||
|
|
||
| ```bash | ||
| cd elt-common/ | ||
| uv venv | ||
| uv install . --editable --group dev | ||
| ``` | ||
|
|
||
| - Run unit tests with: | ||
|
|
||
| ```bash | ||
| cd elt-common/ | ||
| uv run pytest unit_tests | ||
| ``` | ||
|
|
||
| - The e2e tests require a running data platform stack. Use the docker-based setup in `infra/local` | ||
| to start the stack, run the tests and bring down the stack: | ||
|
|
||
| ```bash | ||
| pushd infra/local; docker compose up -d; popd # start the services | ||
| cd elt-common/ | ||
| uv run pytest e2e_tests | ||
| pushd infra/local; docker compose down -v; popd # stop the services | ||
| ``` | ||
|
|
||
| ## Cloud deployment | ||
|
|
||
| - Use the Ansible playbooks in `infra/ansible-docker/` together with the | ||
| `inventory*.yml` files. See the `infra/ansible-docker/readme.md` for role and | ||
| variable guidance. | ||
|
|
||
| ## Pull Request Guidelines | ||
|
|
||
| - When creating pull requests: | ||
|
|
||
| 1. **Read the current PR template**: Always check `.github/PULL_REQUEST_TEMPLATE.md` for the latest format | ||
| 2. **Follow PR title conventions**: Use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) | ||
| - Format: `type(scope): description` | ||
| - Example: `fix(warehouse/accelerator): fix join in model` | ||
| - Types: `fix`, `feat`, `docs`, `style`, `refactor`, `perf`, `test`, `chore` | ||
|
|
||
| **Important**: Always reference the actual template file at `.github/PULL_REQUEST_TEMPLATE.md` instead of using cached content, as the template may be updated over time. | ||
|
|
||
| ## Troubleshooting & tips | ||
|
|
||
| - Docker resource issues: the local compose stack can be resource heavy. Ensure | ||
| Docker Desktop has enough CPU/memory. | ||
| - Ansible role errors: ensure you have required galaxy roles (see | ||
| `infra/ansible-docker/ansible-galaxy-requirements.yaml`) and the correct Python | ||
| and Ansible versions installed. | ||
|
|
||
| ## Where to go next | ||
|
|
||
| - Read `docs/` and `docs-devel/` for high-level architecture and deployment | ||
| instructions. | ||
| - Inspect `warehouses/` for per-warehouse ELT implementations and examples. | ||
|
|
||
| --- | ||
|
|
||
| This file was created to provide a concise, shareable context document for humans | ||
| and LLM-based agents working with the analytics-data-platform monorepo. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.