Add support for different shell export syntax in sendCommand method #2373
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
Signed-off-by: worksofliam <mrliamallan@live.co.uk>
worksofliam
requested review from
SanjulaGanepola and
sebjulliand
and removed request for
SanjulaGanepola
|
👋 A new build is available for this PR based on c04f0e1. |
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.
Introduce support for varying export syntax based on the shell type in the sendCommand method, accommodating both Bash and Bourne shell conventions.
https://unix.stackexchange.com/a/193137
Run this SQL statement to change your shell:
call qsys2.set_pase_shell_info('USERNAME', '/QOpenSys/usr/bin/bsh'), then restart your connection.Tests that use
getAttributesare passing.Will fix #2370.