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
I am using the ecs.Image APIs to build/publish a private Docker image that is then used from my Kubernetes application. There are a few bits of API feedback as a result (full program below):
Should this be in the ecs module? I'd have expected maybe ecr instead?
The choice of image as the name of the method, on the type Image, is unfortunate, as the most likely naming ends up with things like image.image(...).
Related to that, needing to call two things, instead of just one fromPath-like API, is odd.
Why do I need to specify two names for my image, the first when I call fromPath, and the second when I call image on the result?
Why is parent required when calling the image function? As you can see below, there actually isn't a natural parent for my particular example, since building is the first thing we do.
I am using the
ecs.Image
APIs to build/publish a private Docker image that is then used from my Kubernetes application. There are a few bits of API feedback as a result (full program below):Should this be in the
ecs
module? I'd have expected maybeecr
instead?The choice of
image
as the name of the method, on the typeImage
, is unfortunate, as the most likely naming ends up with things likeimage.image(...)
.Related to that, needing to call two things, instead of just one
fromPath
-like API, is odd.Why do I need to specify two names for my image, the first when I call
fromPath
, and the second when I callimage
on the result?Why is
parent
required when calling theimage
function? As you can see below, there actually isn't a natural parent for my particular example, since building is the first thing we do.Full sample program:
I wish I could simply write this as follows:
The text was updated successfully, but these errors were encountered: