In T788#12086, @nrwahl2 wrote:

deprecate (via doxygen comments)

Why no compat header?

In T788#12084, @nrwahl2 wrote:

if we create new values for enum cluster_type_e and use the current names in enum pcmk_cluster_type, we get type-checker errors:

deprecate (via doxygen comments)

On that note, considering that Corosync has been the only supported cluster type for a long time now, I wonder to what extent this stuff even needs to be public. We can always add public API functions again after branching to 3.0.0. Might even make some naming issues easier in the interim, if we can work with things internally without introducing new public names yet.

enum cluster_type_e: deprecate this name and create an equivalent enum pcmk_cluster_type (the enum value names are fine and do not need to be deprecated)

One of the next things on my agenda is to do mass, quick-and-dirty deprecations -- pcmk__*() with public wrapper, no best practices or refactors otherwise, to ensure we get as much deprecated as possible in time.