Host bulk edit parameters, do you use it?

Community
1

We have made the new host index page, into the default hosts page.
After seeing this topic: Foreman host new UI , I started to look into what actions we should add back from the legacy page.
One of the actions I saw was missing is the “Edit Parameters” action. This action is available from the host edit page and the host details page.

I heard and also saw myself that this action is pretty broken, for example: the page crashes if the action is selected and not all hosts have the same parameter.

My question is: Does anyone use the edit parameters action in bulk? If yes, please describe the usage, and can we improve it somehow?

If not, we will just not add it to the new host index page.

Any feedback will be appreciated, thank you!

1 Like
2

I’ve from this from RFCs to the community section because this is more of a question to the users than developers.

1 Like
3

the bulk actions I find essential are

  • power state on/off
  • change host group
  • set build flag / remove build flag

I used to use the remote job or as it is now ‘run all ansible roles’ but my needs have moved away from this as all the people I work with’s automation patterns change

I’ve had use in the past, it’s rare but very helpful to have, for the ‘change puppet master’ parameters, only needed it a few times, but the few times I have needed it, it’s been very powerful on bulk change, oddly I”m going to need it again just before Christmas, but this is once a year type functionality that’s high value when it’s needed, but not often needed.

Happy to discuss the use cases behind these functions if it helps.

2 Likes
4

Yep, we also use it every once in a while to change custom host params (this we do the most), change host groups as well as power off/on etc.

1 Like
5

Thank you for responding. It’s been difficult to find anyone using this feature. Your feedback may influence killing or keeping and redesigning this bulk select action.

@ikonia and @moritzdietz I sent you a private message asking more about your use case, workarounds, and flows. (I am not sure how comfortable you are discussing it publicly)