Podman v5.8

[k9withabone]

Add support for features introduced in Podman v5.8.0:

• .quadlets files
  • Change default stdout output to match the new format.
  • Add podlet --quadlets-file option.
• [Container]
  • AppArmor=

[k9withabone]

@TheRealBecks do you think changing the default stdout output format counts as a breaking change? If so, do you think I should leave the default format as is and only use the new format when the podlet --quadlets-file flag is used?

[TheRealBecks]

@k9withabone What feature do you refer to regarding https://github.com/containers/podman/releases/tag/v5.8.0 ? Which feature/changes states the introduction of .quadlets files?

[k9withabone]

The first one (containers/podman#27384). Also see the podman-quadlet-install(1) man page.

[TheRealBecks]

Okay, I finally got it: There's a new file type .quadlets that can be used as a multi-yaml-file. Therefore it's more like a "special" case to provide the input for Podman.

So no, don't change the default behavior, but use the --quadlets-file flag to provide a single .quadlets file. Doing the other way makes no sense as all tutorials up to Podman 5.7 provided examples with splitted files. And as the Quadlet concept is meant to be a Systemd extension it's good to provide separate files as it's the way Systemd handles the (unit, service, timer, ...) files.

And I think the default way to build complex Quadlets still is to use separate files as it may be simpler to work with.

[k9withabone]

No, I wasn't talking about changing the default way of writing multiple Quadlet files to disk. I agree that separate Quadlet files is generally best. I'm talking about changing the default output when printing to stdout (i.e., when no file writing options are provided). It would be a pretty minor change as the format is already pretty close to what .quadlets files use. I would just need to change the comments at the top of each file. For example, right now with:

podlet compose --pod << EOL
name: test
services:
  test1:
    image: test1
  test2:
    image: test2
EOL

You get:

# test-test1.container
[Container]
Image=test1
Pod=test.pod

---

# test-test2.container
[Container]
Image=test2
Pod=test.pod

---

# test.pod
[Pod]

But I'm thinking of changing it to:

# FileName=test-test1
[Container]
Image=test1
Pod=test.pod

---

# FileName=test-test2
[Container]
Image=test2
Pod=test.pod

---

# FileName=test
[Pod]

[TheRealBecks]

So the lines like # FileName=test-test1 are mandatory for a .quadlets file, so it makes absolutely sense to change that on our side.

That being said: Your example creates a pod that will be used as name and that partly solves in #131

My suggestion: Do it exactly like you already described and add support for Podman v5.8. Afterwards we should take care of the missing name (and --name) feature in #131 to get the same output when not using the .quadlets file