ElasticKube does not pick up new repository setting when GitHub is not accessible
bergtwvd opened this issue · comments
ElasticKube does not pick up new repository setting when GitHub is not accessible (the default repository). It remains in an infinite loop to attempt to clone.
It should regularly check for a new repository setting by the user.
See #127 for more information.
It should be possible to define the default Git Chart repo via an environment variable.