Developer Guide¶
Getting started as a BigRAE developer.
Quick Start¶
- Local Setup - Clone, dependencies, run locally
- Setup - Deploy to AWS or GCP from scratch
- Installation Config -
bigrae.yamlschema and validation - CI/CD - How deployments work
- Secrets - What secrets exist, where they live
- Platform API Development - DRF endpoints, scopes, schema, and error envelopes
- Privacy Notice Shell - Operator-owned
/privacy/content and cookie disclosure - Terraform - Infrastructure patterns
- Cloud Adapters - Cloud abstraction layer
- Principles - Engineering philosophy
- ADR Enforcement - Architecture guardrails and policy checks
Prerequisites¶
- Python 3.12
- Node.js LTS
- Terraform 1.7+
- Docker
- Git
- AWS: AWS CLI v2 with SSO or IAM credentials
- GCP:
gcloudCLI authenticated with target project
Cloud Access¶
AWS - Configure named profiles for each environment:
export PANW_SHIFTER_DEV_PROFILE="your-dev-profile-name"
export PANW_SHIFTER_PROD_PROFILE="your-prod-profile-name"
GCP - Authenticate with gcloud auth login and set the target project.
Repository Structure¶
shifter/
├── shifter/
│ ├── shifter_platform/ # Django web application
│ │ ├── mission_control/ # Main app (ranges, agents, terminal)
│ │ ├── cms/ # Content management (agents, scenarios)
│ │ ├── engine/ # Orchestration services
│ │ ├── documentation/ # In-app docs (you're reading this)
│ │ └── config/ # Django settings
│ └── engine/ # Range provisioner
│ └── provisioner/ # Cloud-specific provisioning (AWS EC2, GDC VMs/pods)
├── platform/
│ ├── terraform/
│ │ ├── environments/ # AWS env configs (dev/, prod/)
│ │ ├── modules/ # AWS Terraform modules
│ │ ├── global/ # Cross-environment resources (IAM, OIDC, runners)
│ │ └── gcp/ # GCP Terraform (modules/, environments/)
│ ├── charts/shifter/ # Helm chart for the GCP control plane
│ └── deployer/gcp/ # GCP deployer image
├── scripts/ # Bootstrap and utility scripts
├── shifter/installation/ # bigrae.yaml parser, validator, backend registry
└── .github/workflows/ # CI/CD pipelines (AWS + GCP)
Git Workflow¶
feature/* ──► dev ──► aws-dev ──► main ──workflow_dispatch──► prod env
│ │
│ ▼
└──────► gcp-dev
│
▼
gcp dev env
- feature/* - Development work
- dev - Integration, validation only
- aws-dev - AWS dev deployment branch
- gcp-dev - GCP dev deployment branch
- main - Production code branch; prod deploys require manual dispatch
All changes go through pull requests. Never commit directly to deploy branches.
Next Steps¶
Start with Local Setup to get the portal running on your machine.