mrutkows commented on issue #498: Do we support manifest.yaml available as an HTTP link URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/498#issuecomment-331038071 @daisy-ycguo The goal was to be able to install a manifest from various "storage" locations. 1) local filesystem 2) http (and https) on a remote a file (manifest, deployment, actions) 3) Object storage (perhaps not via HTTP) - this is expected from AWS Lambda users. Today: ``` -m # points to manifest file -p # points to package location -d # deployment file ``` The PRIMARY use case is to point to the repo/directory where the package is located on the internets (i.e., a URI). Eventually, we wanted to point to an OpenWhisk Package Catalog with a known HTTP REST API (like NPM has for NodeJS packages). In the future, we could do this: ``` -p <URI> # this could be local filesystem, HTTP(S) (e.g., GitHub), or other protocols (we would add support for over time). ``` - if no, -m or -d flags are provided we would try to find the manifest.yaml an deploument.yaml by their default names - if -m or -d provided we would treat it as a ```<relative path>/<file_name.yaml>``` and locate it under the location that ```-p``` flag points to Ideally, this way -p works together with both -m and -d (as optional flags). for example: ``` ./wskdeploy -p "https://openwhisk.net/catalog/packages/"; -m "folder1/manifest_1.yaml" -d "folder2/deploy_2.yaml" ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
