Adding "error path" to the TIM process domains with whois playbook #24604
Conversation
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
altmannyarden
approved these changes
Feb 16, 2023
ayman-m
pushed a commit
to my-soar/content
that referenced
this pull request
Feb 24, 2023
…emisto#24604) * Added an error path so th PB wont stop on unknown tlds. * RN * Added description key where needed. * Update 1_4_10.md * Update 1_4_10.md
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.
Status
Related Issues
fixes: https://jira-hq.paloaltonetworks.local/browse/XSUP-21318
Description
As the playbook fails on unsupported TLDs were adding an error path to allow it to quietly fail.
Screenshots
Minimum version of Cortex XSOAR
Does it break backward compatibility?