You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We hope to avoid bringing legacy dynamic services to the sim4life-deployment.
For this, we need to ideally provide a drop-in modern-style dynamic service replacement for all "published" legacy services. Furthermore, one could check in the projects DB table what other legacy dynamic services are used and should have replacements.
We can use the new service-compatability table to mark the legacy-services as deprecated and provide an option to upgrade to the modern-style replacement.
@sanderegg and @GitHK discussed a potentially viable approach to build modern-style dynamic-service images based on legacy ones, this has to be evaluated.
The text was updated successfully, but these errors were encountered:
We hope to avoid bringing legacy dynamic services to the sim4life-deployment.
For this, we need to ideally provide a drop-in modern-style dynamic service replacement for all "published" legacy services. Furthermore, one could check in the
projects
DB table what other legacy dynamic services are used and should have replacements.We can use the new service-compatability table to mark the legacy-services as deprecated and provide an option to upgrade to the modern-style replacement.
@sanderegg and @GitHK discussed a potentially viable approach to build modern-style dynamic-service images based on legacy ones, this has to be evaluated.
The text was updated successfully, but these errors were encountered: