Fly intercept no longer contains task environment variables set

[dennisjbell]

Not sure if this is new intended behaviour or a bug, but I just upgraded to 7.11.2 from 7.9.1 and was surprised that fly intercept to a task no longer contained the environment variables set for the task from the pipeline. Any idea why this was done? It makes manually running scripts that rely on these variable being set no longer function, and as a lot of those variables get populated from the secret store, a real PITA to resolve manually (not to mention a reduced security level).

[dennisjbell]

Okay, mea culpa -- chose wrong task, that didn't have the envs set. Egg, meet face.