Update dig.py error handling#4732
Merged
blag merged 12 commits intoStackStorm:masterfrom Jul 23, 2019
punkrokk:master
Merged
Conversation
…led. Update readme. Bump pack version.
…led. Update readme. Bump pack version.
blag
suggested changes
Jul 2, 2019
…ded a NOTE to revisit once py3 only.
Member
Author
|
@blag updated based on your requests. |
blag
suggested changes
Jul 19, 2019
Contributor
blag
left a comment
There was a problem hiding this comment.
One small wording change, and add a changelog please.
Other than that, this looks good to go! 👍
blag
approved these changes
Jul 23, 2019
Contributor
|
Thanks for the contribution! |
This file contains hidden or 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
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.
I have added an exception to the linux.dig action script to handle the situation where the
digcommand is not installed, which, it seems on CentOS/RHEL gets the user this error:This doesn't seem to be an issue on Ubuntu. It appears the
dnsutilsis installed. At least on the vagrant st2 dev environment. As you can see there is now a better error message if we get anOSErrorexception, suggesting that dig is either not on the PATH or installed.I have also update the linux pack readme to include the dig action.
Since this is a core pack and installed by default, I opened the below PR to install bind-utils by default in EL7 distros.
StackStorm/st2-packages#619