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
The Fedora CoreOS Config Transpiler (FCCT) will read FCCs and emit Ignition configs (see #129). This mirrors how with Container Linux is configured with CLCs and the Container Linux Config Transpiler (CLCT).
Ignition uses camelCase in it's config currently. CLCT uses snake_case. We should pick one for FCCT.
I'm not what will be more confusing: using a different case than Ignition or being different than CLCT.
Worth calling out we can change Ignition with a major spec bump, but that's a lot of churn and I'd like to avoid it if possible.
The text was updated successfully, but these errors were encountered:
FWIW I also prefer snake case, though very weakly. Talking with @crawford he thinks using snake case with yaml and camel case with json is pretty standard. Snake case also is also what cloudinit uses, so that's a tiny bit less friction for those coming from cloudinit-land.
I'm going to close this out in favor of snake case by EOD friday if no one has a strong case the other way.
The Fedora CoreOS Config Transpiler (FCCT) will read FCCs and emit Ignition configs (see #129). This mirrors how with Container Linux is configured with CLCs and the Container Linux Config Transpiler (CLCT).
Ignition uses
camelCase
in it's config currently. CLCT usessnake_case
. We should pick one for FCCT.I'm not what will be more confusing: using a different case than Ignition or being different than CLCT.
Worth calling out we can change Ignition with a major spec bump, but that's a lot of churn and I'd like to avoid it if possible.
The text was updated successfully, but these errors were encountered: