|
2 | 2 |
|
3 | 3 | ## Quick Start
|
4 | 4 |
|
5 |
| -Auto-graft automatically handles subgraph dependencies when deploying grafted subgraphs. It requires an IPFS endpoint to fetch dependency manifests. |
| 5 | +Auto-graft automatically handles subgraph dependencies when deploying grafted subgraphs. It requires an IPFS endpoint to fetch dependency manifests and must be explicitly enabled. |
6 | 6 |
|
7 | 7 | ### Prerequisites
|
8 | 8 |
|
9 |
| -**Required Configuration - IPFS Endpoint:** |
| 9 | +**Required Configuration:** |
10 | 10 |
|
| 11 | +1. **Enable Auto-Graft (New in v0.24.3):** |
| 12 | +```bash |
| 13 | +# Option 1: Command-line argument |
| 14 | +graph-indexer-agent start --enable-auto-graft |
| 15 | + |
| 16 | +# Option 2: Environment variable |
| 17 | +export INDEXER_AGENT_ENABLE_AUTO_GRAFT=true |
| 18 | +``` |
| 19 | +Default: `false` (disabled - must be explicitly enabled) |
| 20 | + |
| 21 | +2. **IPFS Endpoint:** |
11 | 22 | ```bash
|
12 | 23 | # Option 1: Environment variable
|
13 | 24 | export INDEXER_AGENT_IPFS_ENDPOINT=https://ipfs.thegraph.com
|
14 | 25 |
|
15 | 26 | # Option 2: Command-line argument
|
16 | 27 | graph-indexer-agent start --ipfs-endpoint https://ipfs.thegraph.com
|
17 | 28 | ```
|
18 |
| - |
19 | 29 | Default: `https://ipfs.network.thegraph.com` (if not specified)
|
20 | 30 |
|
21 | 31 | ## Introduction
|
@@ -62,11 +72,12 @@ Before using auto-graft, ensure you have:
|
62 | 72 |
|
63 | 73 | - **Graph Node**: Running with grafting support enabled (grafting is supported on all networks)
|
64 | 74 | - **IPFS Access**: The indexer must be able to fetch subgraph manifests from IPFS (configured via `--ipfs-endpoint` or `INDEXER_AGENT_IPFS_ENDPOINT` environment variable)
|
| 75 | +- **Auto-Graft Enabled**: Starting from v0.24.3, auto-graft must be explicitly enabled via `--enable-auto-graft` flag or `INDEXER_AGENT_ENABLE_AUTO_GRAFT=true` |
65 | 76 | - **Indexer Infrastructure**: Standard indexer setup with indexer-agent and indexer-service
|
66 | 77 |
|
67 | 78 | ## Using Auto-Graft
|
68 | 79 |
|
69 |
| -The beauty of auto-graft is that it requires no configuration or special commands. Simply deploy your grafted subgraph as you would any other subgraph, and auto-graft handles the rest. |
| 80 | +Once enabled with the `--enable-auto-graft` flag, auto-graft requires no additional configuration or special commands. Simply deploy your grafted subgraph as you would any other subgraph, and auto-graft handles the rest. |
70 | 81 |
|
71 | 82 | ### Example Subgraph Manifest with Graft
|
72 | 83 |
|
@@ -170,7 +181,7 @@ When a dependency reaches its target block, auto-graft will:
|
170 | 181 | - Continue indexing past the graft point to ensure the dependency remains available
|
171 | 182 | - Allow the main subgraph to successfully graft from this dependency
|
172 | 183 |
|
173 |
| -*Note: Prior to v0.24.2, dependencies were automatically paused after reaching their target block. This behavior was removed to ensure better availability and prevent issues with allocations.* |
| 184 | +*Note: Prior to v0.24.3, auto-graft was enabled by default when an IPFS endpoint was configured. Starting from v0.24.3, it must be explicitly enabled with the `--enable-auto-graft` flag.* |
174 | 185 |
|
175 | 186 | ## Monitoring Auto-Graft
|
176 | 187 |
|
|
0 commit comments