| Status | |
|---|
| Stakeholders | |
|---|
| Outcome | (See Background) |
|---|
| Due date | When does this decision need to be made by? |
|---|
| Owner | |
|---|
|
Background
As a follow-up to The New Layout for all SIMP Modules
Option 1: Separate Prefixed Variables
Examples:
---
# prefix 1: simp_*
simp_pki: true
simp_client_nets:
- '192.168.0.0/24'
# prefix 2: enable_simp_*
enable_simp_pki: true
# enable isn't a thing for client_nets
simp_client_nets:
- '192.168.0.0/24'
|
|---|
Pros:
Cons:
Option 2: Separate Name-Spaced Variables
Examples:
---
simp::enable_pki: true
simp::client_nets:
- '192.168.0.0/24'
|
|---|
Pros:
Cons:
Option 3: Name-Spaced Hash of Options
Examples:
---
simp::options:
'enable_pki': true
'client_nets':
- '192.168.0.0/24'
|
|---|
Pros:
Cons:
- Individual elements within a Hash are awkward to modify or override
- class parameters
- deep merge or replace?
Action items
- Type your task here. Use "@" to assign a user and "//" to select a due date.