Rather than opening a new ticket i think this is still valid. I am interested in updating rancher using the CLI with the purpose to use the yml files as the sole source of truth. Every commit would potentially trigger a deployment command
$ rancher up --stack StackName --upgrade --force-upgrade
The problem i see with this approach is that some external dependencies and changes might not be handled. for instance i am getting at the moment
INFO[0000] Existing volume template found for stack-elk-data
FATA[0000] Volume “stack-data” needs to be recreated - driver has changed
This is because i want this volume to use rancher-nfs when it was not doing it before. I also have added another external volume in the stack so i can feed files to the service.
If I had to use docker-compose locally I would not get usually any problems doing this. So what am I missing? What do I need to understand about Rancher CLI to achive a real CI/CD process? I dont think the API is fit for purpose for this as I would need to write something custom and I am always happy with the lazy/consistent way (CLI) if it really works.