So far, the environments were coming with a edeploy key. This key was use to point on the .edeploy file location.
With this incoming release, the purpose of this edeploy has been changed. It's not the location of the eDeploy git repository.
The .edeploy file location are now pointed by the newly introduced roles key.
Our problem is simple, it will be impossible to use code from the master branch against env from previous release. The opposite is also true.
We believe it's would make sense to preserve the edeploy key unchanged and introduce a new edeploy_repo to point on the location of the edeploy git repository.
I think this is a serious issue that should be resolved before the release.
So far, the environments were coming with a
edeploykey. This key was use to point on the .edeploy file location.With this incoming release, the purpose of this
edeployhas been changed. It's not the location of the eDeploy git repository. The .edeploy file location are now pointed by the newly introducedroleskey.Our problem is simple, it will be impossible to use code from the master branch against env from previous release. The opposite is also true. We believe it's would make sense to preserve the
edeploykey unchanged and introduce a newedeploy_repoto point on the location of the edeploy git repository.I think this is a serious issue that should be resolved before the release.