Not in tasks, but in plans
# puppet
b
Not in tasks, but in plans
a
Ran out of time yesterday, but I've setup a simple plan that runs the task I'd already built. The plan has a hardcoded (for now) reference to the PE master FQDN. The plan calls the task and passes the user supplied environment variable. It seems to build the specified environment, but then fails overall about 6 minutes later with the below picture. Is the plan automatically trying to sync every known environment from code-staging to code? When I run the task outside the plan, nothing like this occurs, so I think it's a plan thing.