Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toggle features based on what the remotely configured sensor version supports #189

Merged

Conversation

ltsonov-cb
Copy link
Contributor

As requested by product, the remote configurator should prioritize ease-of-use and automatically enable/disable features that the new sensor version supports (if it is provided).

}
}
if sensorMetadataForVersion == nil {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is expected to happen in such case? I guess this means no sensor version was matched right? Do we want to return an error for that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Initially I thought we should return error as well and abandon the change, but the following convinced me otherwise:

  • For customers, the common case is to use the valid versions. We already do a check on the backend when creating the Change - and if the version is semantic, we require that we know about it (so this check here should never be nil). If the version is not semantic, we assume that it is a special version for the customer so we allow the flow to go through - but that should be a rare case for hotfixes or private betas. We don't expect customers to use versions not in the list otherwise.
  • For development flows, this check doesn't make sense as you often have sensor versions that are not in the "main" list and that is OK

So for these cases we assume nothing about the feature support and leave them as-is. Of course, the customer might make an invalid change but we can't verify that.

@ltsonov-cb ltsonov-cb merged commit e8839a1 into develop Oct 5, 2023
2 checks passed
@ltsonov-cb ltsonov-cb deleted the CNS-3719-toggle-features-based-on-sensor-support branch November 8, 2023 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants