Veillard Daniel

since rfc6901 is a fragment identifier specification, I would really suggest for standard and potential future uses to use the syntax # for specifying the path: pointer: #/spec/containers/0/public_ip This means...

Seeing sources: - file://artifacts/kubernetes/template.json params: - foo: #/spec/template/metadata/name urges me to simplify it to params: - foo: file://artifacts/kubernetes/template.json#/spec/template/metadata/name And you have something which is a proper URI Daniel

One nasty thing is that referencing local files is always a bit of a mess, file:// scheme works fine for absolute patch but in practice it's rarely where the files...

no solution, just a warning. for example file:/../foo vs. file:///../foo will get probably more confusion and errors than simply accepting ../foo for relative file paths

Hum, params should really be associated to a given source. If you start giving multiple sources in the current suggested syntax, how do we know on which source the param...

Yeah that works artifacts/kubernetes/template.json#/spec/template/metadata/foo is more web like but it can get repetitive and we already need to provide the URI for the resource so ACK on vavlin suggested syntax

Yes I think that's a very common use case and possibly the largest population we can target from Podman Desktop so it would absolutely make sense, Plus it's a common...

I think there is 2 required sub issues: 1/ Support for WSL2 in the image builder container image: this is already a preview in the online version so hopefully this...