Add parameter to ensure all services absent

[ehelms]

No description provided.

[ekohl]

Isn't there a value to keep this?

[ehelms]

This has proven to mostly cause confusion in the context of the installer as I added it to have more granular control but not intended to be user facing; however, as noted it presents itself that way and leads to confusion.

[ehelms]

There are two elements that cannot be removed right now:

• Volumes
• Network

This is largely due to the relationships and requirements on those by each of the services.

[evgeni]

This means we need to update https://github.com/theforeman/foreman_maintain/blob/master/definitions/reports/iop_remediations.rb#L14 and https://github.com/theforeman/foreman_maintain/blob/master/definitions/features/iop.rb#L5-L8
right?

[ehelms]

Definitely the former, and probably the latter. Right now this change does not remove the network or volumes as those are proving hard to remove due to dependencies.

[evgeni]

theforeman/foreman_maintain#1050

[evgeni]

There are two elements that cannot be removed right now:

• Volumes
• Network

This is largely due to the relationships and requirements on those by each of the services.

Maybe a stupid idea, but can we drop the require of the individual containers on their Volumes and Networks and then do smth like

if ($ensure == 'present') {
  Podman::Network <| tag == 'iop' |> ~> Podman::Quadlet <| tag == 'iop' |>
  Podman::Volume <| tag == 'iop' |> ~> Podman::Quadlet <| tag == 'iop' |>
} else {
  Podman::Quadlet <| tag == 'iop' |> -> Podman::Network <| tag == 'iop' |>
  Podman::Quadlet <| tag == 'iop' |> -> Podman::Volume <| tag == 'iop' |>
}

Maybe even -> instead of ~> and add a subscribe? No, wait, subscribe also enforces ordering. Stupid.

[ekohl]

There's some merit in not destroying the volume so users can easily switch back and forth, but I'd agree with the network part.

[evgeni]

I think the relevant data is in postgres, so it won't be too bad, but I see the point

[evgeni]

There are two elements that cannot be removed right now:

• Volumes
• Network

This is largely due to the relationships and requirements on those by each of the services.

Maybe a stupid idea, but can we drop the require of the individual containers on their Volumes and Networks and then do smth like

if ($ensure == 'present') {
  Podman::Network <| tag == 'iop' |> ~> Podman::Quadlet <| tag == 'iop' |>
  Podman::Volume <| tag == 'iop' |> ~> Podman::Quadlet <| tag == 'iop' |>
} else {
  Podman::Quadlet <| tag == 'iop' |> -> Podman::Network <| tag == 'iop' |>
  Podman::Quadlet <| tag == 'iop' |> -> Podman::Volume <| tag == 'iop' |>
}

Maybe even -> instead of ~> and add a subscribe? No, wait, subscribe also enforces ordering. Stupid.

So I tried this with networks in #74