qualys_vmdr: add support for configuring which cloud metadata to use #10658
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.




Proposed commit message
This adds a UI configurator that allows the user to select which of the two sources (or both) to use to populate the cloud fields. It also tags the document with an indicator of which sources were available.
It's quite extravagant, so I'm not sure of the merits of merging this, but is was what was asked for as the ideal. So here it is.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
cloud.*fields with Qualys data and not elastic agent metadata #10277Screenshots