I’m afraid there isn’t. Ideologically, I don’t think a target should configure itself differently based on what UBT is intending to do with it… In practical terms, I wouldn’t expect it to work reliably because of how we cache actions for the target on the first run. Part of the motivation for refactoring that stuff was to internalize things that had been added into that class that weren’t meant to be visible.