[features test cmd] Write tests with a non-root remoteUser
#286
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, if you set 'remoteUser' in a test, the accompanying test scripts placed into the shared 'workspaceFolder' would not have the appropriate permission bits set to be executed by the exec user. This patch ensure that all files in the workspaceFolder can be read/written/executed by the exec user. A test is added to validate creating a user and setting 'remoteUser' in a scenario, and then running a test within that context to validate.
chrmarti
approved these changes
Nov 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tracking: #139
Previously, if you set 'remoteUser' in a test, the accompanying test
scripts placed into the shared 'workspaceFolder' would not have the
appropriate permission bits set to be executed by the exec user.
This patch ensure that all files in the workspaceFolder can be
read/written/executed by the exec user.
A test is added to validate creating a user and setting 'remoteUser' in
a scenario, and then running a test within that context to validate.