You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/src/content/ignition/docs/guides/deploy.md
+21
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,12 @@ An example file could be called `./ignition/parameters.json` and contain the fol
40
40
}
41
41
```
42
42
43
+
:::tip
44
+
45
+
`JSON5` format is also supported for parameter files!
46
+
47
+
:::
48
+
43
49
This makes the `name` parameter for the `Apollo` module be `"Saturn V"`.
44
50
45
51
To execute a deployment using parameters, you need to use the `--parameters` argument, like this:
@@ -74,6 +80,21 @@ To pass a `bigint` as a Module parameter, you can encode it as a string. Any str
74
80
}
75
81
```
76
82
83
+
You can also define global parameters that will be available to all modules. To do this, define a `$global` key in the parameters file:
84
+
85
+
```json
86
+
{
87
+
"$global": {
88
+
"shouldBeAllowed": true
89
+
},
90
+
"MyModule": {
91
+
"shouldBeAllowed": false
92
+
}
93
+
}
94
+
```
95
+
96
+
In this example, the `shouldBeAllowed` parameter will be `true` for all modules except `MyModule`, where it will be `false`. Global parameters can be accessed in the same way as module parameters.
97
+
77
98
## Inspecting an existing deployment
78
99
79
100
To get a list of all the deployment IDs that exist in the current project, run:
0 commit comments