In release v2.2.0 the kvm entries update command is not accepting true/false as the key value.
This new rule broke the logic of our automation pipeline.
Is there any way around it or would it be possible to accept true/false values in this command again?
In release v2.2.0 the kvm entries update command is not accepting true/false as the key value. This new rule broke the logic of our automation pipeline. Is there any way around it or would it be possible to accept true/false values in this command again?