Initialisation depot

arti-api/auth-service/ACTIVE-CONFIG.md

@@ -0,0 +1,54 @@
+# Active Pipeline Configuration
+
+## 🎯 **Currently Active**
+
+**✅ `.drone.jsonnet`** - Jsonnet-based modular configuration
+- **Location**: Root directory (required by Drone)
+- **Imports from**: `pipeline/common.libsonnet` and `pipeline/build-steps.libsonnet`
+- **Status**: ACTIVE - Used for all builds
+
+## 📋 **Reference Files (Not Active)**
+
+### **Starlark Example**
+- **File**: `pipeline/.drone.star.example`
+- **Purpose**: Reference example of Starlark configuration
+- **Status**: INACTIVE - Example only
+
+### **YAML Variants**
+- **Files**: `pipeline/.drone.yml.*`
+- **Purpose**: Alternative configurations and evolution history
+- **Status**: INACTIVE - Reference/backup only
+
+### **YAML Anchors**
+- **File**: `pipeline/.drone.yml.anchors`
+- **Purpose**: Example of YAML anchor-based factorization
+- **Status**: INACTIVE - Example only
+
+## 🔧 **Configuration Hierarchy**
+
+```
+1. .drone.jsonnet (ROOT)           ← ACTIVE
+   ├── imports pipeline/common.libsonnet
+   └── imports pipeline/build-steps.libsonnet
+
+2. pipeline/.drone.star.example    ← Example
+3. pipeline/.drone.yml.*           ← Backup/Reference
+```
+
+## ⚙️ **How Drone Processes Files**
+
+Drone looks for configuration files in this order:
+1. **`.drone.jsonnet`** ← ✅ YOUR ACTIVE CONFIG
+2. `.drone.star` 
+3. `.drone.yml`
+4. `.drone.yaml`
+
+Since you have `.drone.jsonnet` in the root, **that's what Drone uses**.
+
+## 🎯 **To Make Changes**
+
+Edit these files:
+- `pipeline/common.libsonnet` - Shared steps, environment, triggers
+- `pipeline/build-steps.libsonnet` - Build logic, external Buildah
+
+Then commit and push - Drone automatically processes the Jsonnet!