Fix permission errors when checking SDKMAN install for different user #70
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
When SDKMAN is installed for a different user than the one Ansible is connecting with for the first time, it is likely that the user home directory permissions do not allow traversal for the Ansible user. To fix the problem, let's switch to the root user for this check, which should work in virtually every reasonable case.
|
|
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.
When SDKMAN is installed for a different user than the one Ansible is connecting with for the first time, it is likely that the user home directory permissions do not allow path traversal and/or file reading for the Ansible user:
To fix the problem, let's switch to the root user for this check, which should work in virtually every reasonable case.