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
The porter.yaml file can have image maps defined and the templating supports referencing those images by name. It is currently a dictionary map (which none of the other types do, they are all lists with a name field).
Is it a huge pain to add support for this type as it works right now?
Depends what you mean by "support" grin... you mean something like wigglies if the image or field doesn't exist, and/or completion popups on the bundle.images. prefix?
At the very least it shouldn't squiggle the text "bundle.images.NAME.*" with the porter_no_definition error. If I can have autocomplete that acts like how parameters work, that would be even better. 😁
The porter.yaml file can have image maps defined and the templating supports referencing those images by name. It is currently a dictionary map (which none of the other types do, they are all lists with a
name
field).Is it a huge pain to add support for this type as it works right now?
The text was updated successfully, but these errors were encountered: