Regarding my issues posted Monday and yesterday, is there a way to skip file-sync calls on all environments when puppet-code deploy is called via a plan? It doesn't appear to trigger when the task I use is called directly.

File sync completing to deliver the update to all Puppet Server instances is the ultimate goal of a code deployment. So, it's not really designed to be skippable.

Agreed, though I’d expect to get the same error/timeout when calling the task explicitly. After further delving it just looks like plans create a JRubyPool lock that tasks don't.

Ah, yes. That would be a problem. File sync includes Orchestrator, since it consumes deployed content. Plans run inside of a JRuby instance. So, you've got a plan waiting for the deployment to finish and the deployment waiting for the plan to finish.

That last comment is the kicker. And as you elude, there doesn’t seem like a way around it.

I suppose one thing you could do is call the deploy API with

wait: false

. That should return when the deployment is queued without waiting for file sync to complete.

Then I'd have to come up with some way of getting the result. Just pivoted to a little overkill gitlab pipeline.