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
Actually when deploying to Google Cloud I need to invoke the gcloud docker Command so that I could publish images. (it adds some token refresh mechanism but is actually just a wrapper of docker)
However due to the nature of sbt-native-packager I would need to run two steps instead of one to publish / deploy a new image to gcloud.
The text was updated successfully, but these errors were encountered:
Thanks for your feature request. I'm not sure how this would look like. Adding a way to customize the docker command itself seems like a big change for "1 instead of 2" steps.
I would recommend overriding the docker:publish or docker:publishLocal command.
Furthermore is deployment not in the scope of native packager. This boundary may not be as clear with docker as it is with other packaging formats, but supporting vendor specific deployment tools, is.
Actually when deploying to Google Cloud I need to invoke the
gcloud docker
Command so that I could publish images. (it adds some token refresh mechanism but is actually just a wrapper of docker)However due to the nature of sbt-native-packager I would need to run two steps instead of one to publish / deploy a new image to gcloud.
The text was updated successfully, but these errors were encountered: