So far, the deployment process is entirely automated for all environments and has continued to be successful. Currently, when a tagged release is created, the Helm chart will be templated and packaged the resulting files will be uploaded to the release as assets. However, there are no deployment instructions, so these files essentially become useless without intimate knowledge of helm or kubectl to run them.
This issue proposes that along with the prepared file asset uploads, the release descriptions also get automatically updated with appended deployment instructions that are tailored directly to that release in question so commands can easily be copied/pasted to deploy the application.
The below comments will be the proposed descriptions for these deployment instructions.
So far, the deployment process is entirely automated for all environments and has continued to be successful. Currently, when a tagged release is created, the Helm chart will be templated and packaged the resulting files will be uploaded to the release as assets. However, there are no deployment instructions, so these files essentially become useless without intimate knowledge of
helmorkubectlto run them.This issue proposes that along with the prepared file asset uploads, the release descriptions also get automatically updated with appended deployment instructions that are tailored directly to that release in question so commands can easily be copied/pasted to deploy the application.
The below comments will be the proposed descriptions for these deployment instructions.