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
The default behavior for wskdeploy when pointed to a Package directory is to look for the file "manifest.yaml"; however, our own "usecases" name the file "manifest.yml" (i.e., .yml versus .yaml) and fail.
Please allow the code to look for both .yaml and .yml extensions by default.
For example, our test (usecase) for webhook has instructions:
wskdeploy -p /tests/usecases/webhook
However, this fails with:
2017/07/19 08:33:22 missing manifest.yaml file
because the Manifest file is actually named "manifest.yml"
The text was updated successfully, but these errors were encountered:
mrutkows
changed the title
wskdeploy default finds manifest.yaml, but not manifest.yml
wskdeploy -p finds manifest.yaml, but not manifest.yml
Jul 19, 2017
The default behavior for wskdeploy when pointed to a Package directory is to look for the file "manifest.yaml"; however, our own "usecases" name the file "manifest.yml" (i.e., .yml versus .yaml) and fail.
Please allow the code to look for both .yaml and .yml extensions by default.
For example, our test (usecase) for webhook has instructions:
However, this fails with:
because the Manifest file is actually named "manifest.yml"
The text was updated successfully, but these errors were encountered: