Use of __env__ in file_roots master configuration declaration #67045
-
Hi everyone. I'm hoping you can offer some guidance regarding the use of I am using Salt 3007.1 on the latest x86_64 Amazon Linux 2023 directly from the new Broadcom RPM repositories:
The documentation I have been referring to is:
We have a number of different teams and engineering staff who need to be able to test their branches of Salt state and pillar changes prior to merging into our Git SCM that contains all our Salt states. Previously we had uses the Salt native GitFS functionality, but due to the enormous size of our repositories and large number of branches, the performance was unusable (the GitFS implementation was an order of magnitude slower than just pointing to plain directories on the local filesystem). For that reason, we now have a GitLab CI job that just pushes the new branch changes to the Salt master filesystem. This works well, and fast. In the past we were using Salt 3004, which did not support the use of We have read that as of Salt 3005, use of However, we have found that it only seems to reliably work for the When we use it in the
Is there something obviously wrong we are doing here? Have is misunderstood the documentation? Very much hoping someone can offer their insight and assit here. Thanks all! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
A follow up -- this is obviously some failing in our janky Salt configuration. Testing out the most minimal test case does not reproduce the problem -- it works as documented. For anyone else who was seeing anything similar:
|
Beta Was this translation helpful? Give feedback.
A follow up -- this is obviously some failing in our janky Salt configuration. Testing out the most minimal test case does not reproduce the problem -- it works as documented.
For anyone else who was seeing anything similar: