Version Control for Template

[marswong]

Is your feature request related to a problem? Please describe.
I need to iterate my template frequently, since there's no version control for template, I can only delete the existing template and rebuild it, it's ok for testing but really unsafe for production usage.

Describe the solution you'd like
Currently the template seems to be just a docker image, it'd be nice to have the same version control as Docker, like you could use an image with tag and sha256 hash, user could manage the template versions on E2B console like listing available versions and disabling target version, if user find a version with malware, he could disable it.

Consider audit requirements and production availability, we'd better not support deleting a version, if the client request a disabled version, just repond an error.

[linear]

ENG-3243

[dobrac]

Hi @marswong, we're currently working on introducing a versioning of templates. That should help you with production readiness of specific builds.

As of now, the approach we encourage is to use different alias for the template you're iterating frequently on, and the template that's running in production. When you're done, change the alias of the final template to the production one and rebuild it (most of the layers should be then reused from the cache).

There is no need to delete the template when rebuilding, we have versioning of the templates internally, so only after the template is built successfully, new version replaces the old one (you can think of it as if we have now just the latest Docker tag for all builds).