refactor the publishing of the runtimes to move the version of the language in the tag
Closed this issue · 2 comments
To publish our runtimes into the apache organization we have to stick to a fixed set of runtimes. So we have to move the version of the language fron the name (runtime-python-v311:) to the tag (openserverless-python:3.11-0.1.0.timestamp).
Afther this we have to publish in the apache docker hub and automatically update a runtime.json to be published in the runtime repo.
Looks like we finally got the image so we can now try to publish them on the apache github repo, refactoring the names to use the tags for the language version
We have an initial set of images under the apache repository for the operator, runtime-common, and also go, python, nodes and php.
operator and common images have been pushed from the respective official apache GitHub repos, used the ASF DockerHub enforced secrets.
The remaining images, are using s dedicated docker cloud build which is currently running under another docker hub account. ASF enforced secrets do not have access to the docker cloud builder, so current images have been pushed from a forked repository.