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.
Support shorter syntax for addressing the current dependency's outputs, using ${outputs.OUTPUT_NAME} instead of ${bundle.dependencies.CURRET_DEP.outputs.OUTPUT_NAME}.
The output variable is only applicable within the outputs section of a dependency and both formats are still supported.
What issue does it fix
Closes #2662
Notes for the reviewer
As stated in #2662 we should determine if we want the variable name is too close to bundle.outputs.
Checklist
[X] Did you write tests?
[x] 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
Support shorter syntax for addressing the current dependency's outputs, using
${outputs.OUTPUT_NAME}instead of${bundle.dependencies.CURRET_DEP.outputs.OUTPUT_NAME}. The output variable is only applicable within the outputs section of a dependency and both formats are still supported.What issue does it fix
Closes #2662
Notes for the reviewer
As stated in #2662 we should determine if we want the variable name is too close to
bundle.outputs.Checklist