Allow trusting custom integration fingerprints #42
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.
This adds three new
ImportAssetattributes to allow custom integrations to specify that their fingerprint data should be trusted, even if the data cannot be normalized by runZero's fingerprint engine:trust_os- Trusts theosattribute and use it to set Asset OStrust_os_version- Trusts theos_versionattribute and use it to set Asset OStrust_device_type- Trusts thedevice_typeattribute and use to to set Asset TypeWithout these options set,
os,os_versionanddevice_typewill only be used to set the runZero asset fingerprint if they can be normalized via runZero's fingerprint engine.os,os_versionanddevice_typeare always available under the custom integrations attributes, even when the correspondingtrust_*options are not set.Example: