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
With #2808 we merged the jibMaven and jibGradle blocks into a single jib block where we determine the plugin-type based on the presence of key files like build.gradle. This isn't fool-proof and we should allow setting the value explicitly.
The text was updated successfully, but these errors were encountered:
// PluginType defines the different supported Jib plugins.
typePluginTypeint
const (
// use `iota+1` so that 0 is an invalid value
JibMavenPluginType=iota+1
JibGradle
)
I had originally placed this enum definition inside the schema package, with appropriate MarshalYAML() and UnmarshalYAML() functions. This supported validation during the unmarshalling phase, but the schema generator didn't support these enums and so I backed it out.
With #2808 we merged the
jibMaven
andjibGradle
blocks into a singlejib
block where we determine the plugin-type based on the presence of key files likebuild.gradle
. This isn't fool-proof and we should allow setting the value explicitly.The text was updated successfully, but these errors were encountered: