How to limit user-initiated change of Service retires_on?

[MajorDallas]

When a user goes to their active Service in the service ui, then to the Lifecycle dropdown, they can change the retirement date for the whole service.

In the logs, I can see some api logs, one evm log, and an audit log indicating that this has happened.

However, there does not seem to be any corresponding Event in the Automation Engine or Policy. So, I have no idea which state machine or class I should copy+modify or which Event to use as a policy trigger in order to enforce that a user can't sent a date arbitrarily far in the future, eg. they'd be limited to 30 days from Service.created_on.

When I asked some colleagues that have more experience with MIQ, one of them had added a different button to their service dialog that triggers a wholly separate state machine. This works for them, but the original Lifecycle button is still there, allowing arbitrary dates to be set. They cover over that gap with other policies, but since I can't seem to find any information about when the relevant events fire (or, indeed, what events are relevant) I feel like I can't rely on a policy-based solution.

My intuition was that there would be a "Service Reconfigure" event, or that since the api calls Api::ServicesController.retire_resource the "Service Retire" event would be the place to look. My only remaining guess was customizing the RetireService instance and method, but since that starts off by marking the service as retired and that does not happen when only changing the retire date, I'm out of guesses.

[Fryguy]

@agrare Can you take a look at this one?

[MajorDallas]

I've been poking through code hoping to find a clue. Eventually I got to manageiq/app/models/mixins/retirement_mixin.rb, where two retire methods are defined. The second one (line 86) seems to handle both the "retire right now" case and the "retire on this new date" case.

Back in the Automation Engine, I see the retire_service method is effectively empty, as is validate_request. "Somewhere" the AE knows to call RetirementMixin.retire, and that's the part (I think) I need to tap into. I'm just not sure how... All I need is one if block to check a couple dates and either refuse to proceed or let the built-in code take over. I think I can copy one of those methods into my own Domain and it only needs something like this:

if $evm.root['miq_request'].options[:retires_on] > $evm.root['service'].created_on + 30.days
    raise 'some error message'
end

... but when I tried it, it seems neither method actually gets called, like the whole Service retirement state machine is not involved in the process.