Katello features a lot of remote action related Ui bits for installing/updating packages. The current UI buttons/elements are always present, and subset of options are hidden when REX is not present.
It was also expressed in a recent meeting to have REX automatically deployed with a katello dev environment, so the question came up if should be done so in production as well.
This presents us with a couple of options:
- Require REX with Katello at a gem level and installer level. Remote actions work out of the box similar to today.
- Hide UI bits for errata/package actions if REX isn’t present
Let me know if there are other options that i haven’t considered.
From a user perspective I tend to lean towards the first option, as it gives a simpler setup. It also reduces code complexity to make assumptions around its presence.
I’m not sure if there are any gotchas from a build perspective though.