Removing lidar polling config param #229
Merged
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.
Changes proposed in this pull request:
lidar_scanner_interval
property - it was a blocker for specific use cases and not offering any platform wide benefit - this was a primary Pages usage blockerlidar_scanner_interval
but keepingdefault_check_interval*
resources in the config - we set default intervals for resource checks but allow specific resources to increase their interval usingcheck_every
in their resource definitionssecurity considerations
n/a