Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
Building and publishing the server image during a canary build, did not use the canary tag, instead it used the version of the build, e.g., v1.1.0-7-gd0387ecb. It also means that on each canary build a new tag is used when publishing the image.
By checking if we are doing a release of a tagged version or a canary build we can use the correct tag.
Checklist
[ ] Did you write tests?
[ ] Did you write documentation?
[ ] Did you change porter.yaml or a storage document record? Update the corresponding schema file.
[ ] If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇♀️
What does this change
Building and publishing the server image during a canary build, did not use the canary tag, instead it used the version of the build, e.g., v1.1.0-7-gd0387ecb. It also means that on each canary build a new tag is used when publishing the image.
By checking if we are doing a release of a tagged version or a canary build we can use the correct tag.
Checklist