openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Rutkowski" <>
Subject Re: Re: rationale for wskdeploy Docker image
Date Tue, 09 Jul 2019 17:32:22 GMT
I too questioned the "wskdeploy" image (need) during my review, but 
assumed someone (likely in IBM but perhaps elsewhere as well) may still be 
using it for server-side deployment; that is, they utilize the image from 
the project 
(which indicates it is hardcoded to an old iamge tag, but users likely 
ref. "latest"). 

However, when I reached out to a logical contact who worked on this 
functionality within IBM, she indicated that she was not aware if this 
image was being actively used/referenced any longer (although I suspect it 
is). Was hoping Mark Deuser would comment if this is being used by IBM to 
deploy packages server-side any longer.

It is my belief something will break somewhere for some user, but until 
(if) package-deploy becomes a released repo. (which perhaps may morph the 
discussion) and no one steps up ...  FWIW, I think server-side wskdeploy 
usage is a great feature with lots of potential and then having the 
convenience binary avail (that matches the wskdeploy client version) may 
have value.


From:   Rodric Rabbah <>
Date:   07/09/2019 03:13 AM
Subject:        [EXTERNAL] Re: rationale for wskdeploy Docker image

I think we don’t need it but defer to those who worked on it. 

I’d like to also ask at the risk of broadening the original question: 

- should we fold the repository into the cli? 
- or is there a good reason to keep it as a separate deploy tool 
independent of the cli? 


> On Jul 3, 2019, at 4:23 PM, David P Grove <> wrote:
> Do we really need to be publishing a wskdeploy image to dockerhub?
> I'm not understanding why this image needs to be public (it appears to
> perhaps be an image for building wskdeploy?).
> thanks,
> --dave

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message