JHT_Seattle
Hot Shot
Hot Shot

A new PATH issue introduced in 2.7.0?

Jump to solution

If someone else can confirm this, that'd be great.

I've added a location to my PATH variable while provisioning a new stack, but it isn't being applied when the stack is attached.  I updated the stack to check and, frustratingly, my location is in the PATH variable.  So it's in the stack, but it doesn't apply when attached.

0 Kudos
1 Solution

Accepted Solutions
JHT_Seattle
Hot Shot
Hot Shot

Apparently the issue is more with the 2.6.0 agent.  When I updated a VM to the 2.7.0 agent, the PATH variable is correct and reflects what was added in the stack.

View solution in original post

0 Kudos
1 Reply
JHT_Seattle
Hot Shot
Hot Shot

Apparently the issue is more with the 2.6.0 agent.  When I updated a VM to the 2.7.0 agent, the PATH variable is correct and reflects what was added in the stack.

0 Kudos