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
Archive sharing can be important. While wisk deliberately makes archive creation/maintenance a trivial thing, it currently has no particular support for fetching or hosting archives - which is still a useful feature.
The first positional parameter should be amended to allow for http/https URLs as well as paths. If a URL is given, the remote file is fetched, saved to a temporary directory, and used as the skeleton. This must only work for archives, not for arbitrary paths or FTP-like manifests.
Corrospondingly, the -a flag should allow for http/https URLs as well as paths. If a URL is given, the remote file is fetched and registered.
In neither case should users be prompted for authentication. If such a thing happens, failing immediately should occur. That will be covered in a separate issue.
The text was updated successfully, but these errors were encountered:
Archive sharing can be important. While
wiskdeliberately makes archive creation/maintenance a trivial thing, it currently has no particular support for fetching or hosting archives - which is still a useful feature.The first positional parameter should be amended to allow for http/https URLs as well as paths. If a URL is given, the remote file is fetched, saved to a temporary directory, and used as the skeleton. This must only work for archives, not for arbitrary paths or FTP-like manifests.
Corrospondingly, the
-aflag should allow for http/https URLs as well as paths. If a URL is given, the remote file is fetched and registered.In neither case should users be prompted for authentication. If such a thing happens, failing immediately should occur. That will be covered in a separate issue.
The text was updated successfully, but these errors were encountered: