improve documentation for instance versioning with provider instance extension.
Both moduledoc and livebooks. For major versions we should have a test case.
Subsequent Major versions would typically be supported concurrently by having Broadband and BroadbandV2 each with new uuid, but same name and different major_version. Migration of instances is simply by label swap, along with changing specification relationship to new edge. Of course other migrations may be required, and a domain migration could be built.
Test Add a livebook on provider instance versioning, showing the lifecycle and concurrent operation, and first a patch, then a minor change, then a major change. For the major change we will define Broadband and create an instance, then define BroadbandV2 and create an instance, then migrate the original service using cypher. Let's assume it is a breaking change, such as the removal of enum value (like a FTTB from the technology types).
improve documentation for instance versioning with provider instance extension.
Both moduledoc and livebooks. For major versions we should have a test case.
Subsequent Major versions would typically be supported concurrently by having Broadband and BroadbandV2 each with new uuid, but same name and different major_version. Migration of instances is simply by label swap, along with changing specification relationship to new edge. Of course other migrations may be required, and a domain migration could be built.
Test Add a livebook on provider instance versioning, showing the lifecycle and concurrent operation, and first a patch, then a minor change, then a major change. For the major change we will define Broadband and create an instance, then define BroadbandV2 and create an instance, then migrate the original service using cypher. Let's assume it is a breaking change, such as the removal of enum value (like a FTTB from the technology types).