Allow "0" or empty credential_id in create_scanner #759
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 the command only accepted the attribute missing completely to set no credential.
The functions create_task_check_config_scanner and modify_task_check_config_scannerfunction were missing cases for the new scanner type.
mattmundell
approved these changes
Sep 27, 2019
|
Could you please update the API docs too? |
1 task
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.
Previously the
create_scannercommand only accepted thecredential_idmissing completelyto set no credential. Now it also accepts "" and "0".
Also, the task config checks did not recognize the new scanner type.
Checklist: