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
Follow-up to #191/#192, this issue/PR combo exists because the list of projects to get an image from when an image family is specified in a template is hardcoded in the plugin.
This doesn't scale, and implies that users wanting to use an image from one of those plugins should open an issue and us maintainers have to add the project to the list, then release a new version of the plugin.
Instead, we should probably add a new attribute so users that want an image from a specific project/family have the option to specify it manually, and we don't need to release a new version of the plugin each time.
The text was updated successfully, but these errors were encountered:
Follow-up to #191/#192, this issue/PR combo exists because the list of projects to get an image from when an image family is specified in a template is hardcoded in the plugin.
This doesn't scale, and implies that users wanting to use an image from one of those plugins should open an issue and us maintainers have to add the project to the list, then release a new version of the plugin.
Instead, we should probably add a new attribute so users that want an image from a specific project/family have the option to specify it manually, and we don't need to release a new version of the plugin each time.
The text was updated successfully, but these errors were encountered: