Make the new path available in the same run about puppet-windows-path HOT 2 CLOSED

This behaviour could be caused by two different issues:

1. Maybe the current environment of the process in which puppet runs is not updated with the new PATH. After writing the new path, I'm sending a broadcast event that the environment has been updated, so in theory that should not be the problem, but I'm not completely sure if that works under all circumstances. It could be something similar to the behaviour you will see when you
   • start a command prompt in windows
   • change the PATH variable - but not in that command prompt, let's say you change the PATH throught the system control panel
   • the PATH change will not take effect in the command prompt window you opened earlier but only in command prompt windows you open after you changed PATH
2. What exactly does the pip provider do to check for the command in the path? Do you know? If it's using the $::path fact from facter, there is also the problem that the fact will not be updated during the puppet run. As far as I know, it is not possible to update a fact during a puppet run and it probably also would not make sense. See this discussion on the "puppet uses" list.

from puppet-windows-path.

Maybe the pip provider could be changed so that it either takes the pip executable's absolut path as an optional parameter or it takes additional directories it should look in as an argument. In your context, you probably know very well where the pip executable is.

from puppet-windows-path.