-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set scope to machine for imageBuildContextPath #1791
Conversation
According to the docs the "machine" scope can be set in "user or remote settings". So changing the scope does not really prevent setting Am I reading the docs wrong? |
Well, that's how it is written in the docs:
I had to try it to ensure I understand it correctly, here is what I did:
So this confirms what I understand about the property, where "User" settings do not get used in remote scenarios if the scope is set to "machine", and vice versa. I think the documentation needs to explain it further by using a proper example, the linked issue has more details to it as well. |
Allright, thanks Hani, what you are saying makes sense. The docs are confusing 😐 |
Co-Authored-By: Karol Zadora-Przylecki <[email protected]>
* Set scope to machine for imageBuildContextPath * Update package.json Co-Authored-By: Karol Zadora-Przylecki <[email protected]> Co-authored-by: Karol Zadora-Przylecki <[email protected]>
This will essentially avoid reading this setting (if set in the User settings) in remote scenarios, which makes sense since the path might not make sense when running in a container/WSL.