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
on the other hand there is no proper way to set a dynamic version in a recipe.yml using gdk
So the only solution is to make some hacks in the ci/cd pipeline to modify recipe.yml with a version number of what would be the next component version and then build/publish. Instead of simply providing the version as COMPONENT_VERSION like on the s3 artifacts
The text was updated successfully, but these errors were encountered:
Feature Description
It should be possible to use ex. COMPONENT_VERSION in a docker artifact like it is in the s3 artifact
This makes it possible to use images versioned together with the component
Use Case
Right now on one hand using :latest for docker image version are not working (according to this https://repost.aws/questions/QUQGCzc1QgR9C2asXgSwHsnw/how-to-ensure-that-the-most-recent-version-of-a-docker-container-image-is-being-used-when-deploying-a-greengrass-component)
on the other hand there is no proper way to set a dynamic version in a recipe.yml using gdk
So the only solution is to make some hacks in the ci/cd pipeline to modify recipe.yml with a version number of what would be the next component version and then build/publish. Instead of simply providing the version as COMPONENT_VERSION like on the s3 artifacts
The text was updated successfully, but these errors were encountered: