Documentation does not describe how to upgrade services

[navarr]

I was recently asked for help with how to define the version of a warden project's service. After helping, I went to point them to the documentation but could not find it myself.

Either it does not exist, or it is not easily discoverable.

I may contribute this myself, but not right now - hence, the ticket :)

[davidalger]

how to define the version of a warden service

When you say this, do you mean global service or project service? I would assume project, as the global services are generally defined by the Warden release, but just want to make sure it's clear what's being documented here.

[navarr]

@davidalger project. I've updated the main text to clarify.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[hardyjohnson]

@navarr I can probably pick this up this week.

This documentation would describe how to update a project service with the following use cases.

1. As a user I would like to update the version of a service such as PHP in a Magento environment from 8.1 (default for env-init) to 8.2.
2. As a user I would like to update the version of a service with my own docker image.
3. As a user I would like to pull the latest version of an image from the docker container registry.
4. Adding or linking to a bit about adding / overriding configuration for an upgraded service if service config changes between versions.

This would probably mean re-writing some of this https://docs.warden.dev/environments/customizing.html into service specific terminology and covering editing of the local .env, .warden/warden-env.yml, pulling images from the registry and reloading the configuration.