I wouldn't say "Pro is the only production environment" yet. I'm getting ready for the day, far in the future, when there is no more Arc Map, and developing plans to accomplish the same things I need to in Pro. My next "Mountain" to climb is GP History and Metadata Management in Pro. I'm also working on a SQL solution to this answer with some success, but that doesn't help my FGDB users. So, what's it going to take to get https://community.esri.com/external-link.jspa?url=https%3A%2F%2Fsupport.esri.com%2Fen%2Ftechnical-ar... working in Pro? There are still going to be folks that change no setting related to storing GP history despite 25 emails and laminated posters asking them to turn it off, then wonder why the GP history takes up 90% of the GDB size. In response to Dan, I need to account for a more robust environment where I have less control of how folks are provisioning and editing data in Pro. They are not going to be running any Python, trust me. Long story, but the onus is on me to keep things running smooth and not say "no", hence the quest for what I hope will be an automated solution to removing the GP history using Pro. I'm starting with Python, 'cuz I can attach it to task scheduler. Dates are not clear yet, but I'm working on my base OS images that have Pro on them now and testing them thourougly. What 2.2.1-? contains will govern if that image get rolled out this year.
So the take home message is despite what is my [opinion of] Pro, I'm getting ready for it, and working out all of these problems for the day when I do call TS, and am told "We're not supporting Arc". The other message I'm hearing is there is no way to delete GP history from a GDB using Pro, which is very concerning.
Sounds like another "Idea".......