Make additional bundle metadata available to template

[getporter]

Make additional bundle metadata available to template

[carolynvs]

@dev-drprasad It is still needed. The code where these values are resolved has moved. The code where these values are set is now located here:

https://github.com/deislabs/porter/blob/790e7f97542ef2ae85b04594a145692a630bff26/pkg/config/runtime-manifest.go#L164

I realize that the template paths that I used in the issue were incorrect as well. I said bundle.metadata.name, but it is bundle.name. I'll update the original issue to correct that.

[carolynvs]

At the moment, yes. It's out of scope for this issue to change that. We do want to change this so that we can use templating anywhere.

[carolynvs]

I recommend not exposing some fields for dependencies. InvocationImage is one of them.

A bundle can have multiple invocation images and it can be selected by the user when they run the bundle. We are still working on the dependencies spec, and invocationImage is one of the values that won't be something that can be determined after the bundle was executed. There may not be much value anyway in knowing the invocation image executed by a dependency (that remains to be seen as we collect use cases and feedback). So for now let's just leave it off.

Thanks for checking! 👍

[nunix]

oh nice, for my "next crazy evolution" of WSL+CNAB I would need something like:
bundle.dependencies.myOtherBundle.invocationName

as a readonly field of course, as the bundle would be already installed

Looking forward to this one 😈

[dev-drprasad]

@carolynvs is this feature still required ? If yes, i would like to pick it up

[dev-drprasad]

@carolynvs is substitution/templating possible only in actions ?

[dev-drprasad]

@carolynvs I found that Bundle has multiple InvocationImages and there is no name field in InvocationImage struct. Then how authors can do something like bundle.dependencies.mysql.imageName.invocationImage ?