search

boson-project / buildpacks

Boson Project function buildpacks
Apache License 2.0
5 stars 11 forks source link

Figure out image tags/versions #5

Closed lance closed 4 years ago

lance commented 4 years ago

Currently we are modeling our images based on the official buildpack samples. However tagging and versioning are a little confusing in this model.

For example, all of the "stack" images are named faas-stack-* where * is base|build|run and the tags are the language. For example, to use the Node.js run image, you would use quay.io/boson/faas-stack-run:nodejs. This is clean looking but implies a floating tag. Should we also be tagging specific version numbers? E.g. quay.io/boson/faas-stack-run:nodejs-1.0.0.

The actual buildpack images are slightly different than the stack images. For the buildpack images, we are creating for example quay.io/boson/faas-nodejs-bp. The image itself distinguishes it as a Node.js buildpack. Currently there is nothing but a latest tag on the buildpack images. We should determine how we want to version these.

lance commented 4 years ago

/cc @boson-project/core

lkingland commented 4 years ago

Adding an additional tag with the version suffix is a good option, because we then let the user decide which suits their situation better.

lance commented 4 years ago

Closing as this has been addressed in multiple PRs and automated CI/publication of images.