View the latest documentation 5.5
Currently, Lenses CLI command lenses-cli provision is a method used to provision only initial configuration when Lenses is deployed from scratch. Consecutive runs of the provision command are not supported currently, and may have unintended consequences.
lenses-cli provision
Based on this, Lenses CLI provision does not allow for a true “GitOps” workflow. Specifically the following deployment methods, by default skip provisioning from the CLI, using --setup-mode flag as in the next section
provision
--setup-mode
In order to help with configuration race conditions between the Lenses UI wizard and Lenses CLI provision, we can opt for CLI provision command to wait until wizard setup, has been completed. When --setup-mode is used as a flag for CLI provision command: lenses-cli provision the behavior depends on the phase of Lenses deployment:
Lenses UI
Lenses CLI
To help showcase this behavior let’s consider these scenarios:
lenses.provision.enabled
true
On this page