Plugins » Foreman Remote Execution

Scenario:

1. run a job in a specific org/location
2. select 'any context'
3. re-run the job

Actual result:

- the job gets executed in unlimited scope
- technically, this behaviour is not completely wrong, but it's surprising and can be unexpected: I can have one job that runs against my 10 hosts in specific org/location, and when I re-run the very same job later and I'm not careful, it can run 10000 hosts of my infrastructure

Expected result

1. the default context for the stays the one that was in the original job
2. in case different taxonomy is used in the mean-time, there should be a warning
3. alternatively to 2, we could even prevent showing the job that would be assigned to different taxonomy, basically making the jobs taxable (but ideally with 1:n mapping (as we have in host) as opposed to m:n (as we have in other taxable resources). See also https://projects.theforeman.org/issues/20674