Originally reported on Github[1], cloud-init released a change in the cli[2] that broke former cloud-init cli commands.
Previously `cloud-init -f <file> init` was allowed, but after the 24.1 SRU release to Jammy, this broke and
now the following invocation is required to accomplish the same thing: `cloud-init init -f foo.cfg`. There is apparently no syntax that is compatible with both versions.
This is a change in behavior that was released under SRU back to stable releases.
Originally reported on Github[1], cloud-init released a change in the cli[2] that broke former cloud-init cli commands.
Previously `cloud-init -f <file> init` was allowed, but after the 24.1 SRU release to Jammy, this broke and
now the following invocation is required to accomplish the same thing: `cloud-init init -f foo.cfg`. There is apparently no syntax that is compatible with both versions.
This is a change in behavior that was released under SRU back to stable releases.
[1] https:/ /github. com/canonical/ cloud-init/ pull/4559# issuecomment- 2084860007 /github. com/canonical/ cloud-init/ pull/4559
[2] https:/