As a developer, when I start putting PR's out against the main branch, sometimes there are additional non-code related changes that need to get deployed with the code change.  You can find examples of times we've needed to do this in our subscription watch release checklist

To support the "shift left" efforts, it's best if we come up with an automated way to do these tasks, so it's truly automated and a developer doesn't need to sit there waiting for the deploy to be done to ensure they do the additional step if the task is time dependent e.g. "this internal api needs to be ran before the next tally".

A preliminary idea I had is to leverage CJIs for these kind of things.

Example: curl -X POST -H "x-rh-swatch-psk: placeholder" http://localhost:8000/api/rhsm-subscriptions/v1/internal/tally/sync-remittance

Grooming questions:

• What kind of extra "after the deploy has happened" tasks have we encountered in the past?
• Would we consider the org id migration stories (SWATCH-290 and SWATCH-107) in the same category, or is that effort completely a one-off situation?  Those stories have a util linked in the description...maybe that is worth looking at for ideas of our own util?