Commit 4b7ae2f
committed
CLI Option for naming servers as the BMC objects
While the redfish standard supports an API with multiple
systems managed by one endpoint (such as Cisco IMC and others),
an often use-case is to communicate with the BMC directly.
In Netbox, one usually models the system managed by the BMC
and the BMC itself is just an attribute on the system.
The expectation in these circumstances is, that the Server
is not a child of the BMC (i.e. suffix -system-0), but
they are both belonging to the same server (i.e. have the same
name).
The CLI option disable-server-name-suffix allows one to opt-in into the
logic that such a Server should be named as the BMC.1 parent 8261698 commit 4b7ae2f
File tree
3 files changed
+19
-8
lines changed- api/v1alpha1
- cmd/manager
- internal/controller
3 files changed
+19
-8
lines changedSome generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
82 | 82 | | |
83 | 83 | | |
84 | 84 | | |
| 85 | + | |
85 | 86 | | |
86 | 87 | | |
87 | 88 | | |
| |||
128 | 129 | | |
129 | 130 | | |
130 | 131 | | |
| 132 | + | |
| 133 | + | |
131 | 134 | | |
132 | 135 | | |
133 | 136 | | |
| |||
299 | 302 | | |
300 | 303 | | |
301 | 304 | | |
302 | | - | |
303 | | - | |
304 | | - | |
| 305 | + | |
| 306 | + | |
| 307 | + | |
| 308 | + | |
305 | 309 | | |
306 | 310 | | |
307 | 311 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
34 | | - | |
35 | | - | |
36 | | - | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
37 | 38 | | |
38 | 39 | | |
39 | 40 | | |
| |||
161 | 162 | | |
162 | 163 | | |
163 | 164 | | |
| 165 | + | |
| 166 | + | |
164 | 167 | | |
165 | 168 | | |
166 | | - | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
167 | 174 | | |
168 | 175 | | |
169 | 176 | | |
| |||
0 commit comments