Yes, that change to `enterprise_tasks` was intenti...
# puppet-enterprise
c
Yes, that change to
enterprise_tasks
was intentional. That module was always intended to be internal-use only and should have been named something like
pe_internal_tasks
. I think a sub-set of "safe" tasks has been left publicly exposed. There are some items in there that are outright dangerous if not run exactly as expected by
puppet-enterprise-installer
or one of the
puppet infra
sub-commands. For example, if you go by title alone,
enterprise_tasks::pg_basebackup
sounds like it would back up the Postgres database in some way. It does not. It nukes the database data directory and then runs the
pg_basebackup
CLI to pull a copy from some other Postgres instance. Does exactly what
puppet infra provision replica
needs it to do, and disastrous if naively run against the Primary.
j
sounds to me like it should have a different name, so people aren't tempted to run it by mistake. (a big factor in how i do things every day is trying to protect people from themselves)
c
Re-naming is a whole thing in and of its self. That's why this task and many others were hidden in recent PE versions --- so they don't show up in task lists.