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
When I try to archive a bundle that has a slash in the bundle name, archive fails.
To Reproduce
$ porter archive whalegap.tgz --reference ghcr.io/getporter/examples/whalegap:v0.2.0Writing logs to /Users/carolynvs/.porter/logs/01G57B1W09P2FB11DQHJYRPBQV.jsonWriting logs to /Users/carolynvs/.porter/logs/01G57B1W09P2FB11DQHJYRPBQV.jsonWriting logs to /Users/carolynvs/.porter/logs/01G57B1W09P2FB11DQHJYRPBQV.jsonWriting logs to /Users/carolynvs/.porter/logs/01G57B1W09P2FB11DQHJYRPBQV.jsonmkdir /var/folders/mv/cx7sy9c54wn741p4x6v0_t100000gn/T/examples/whalegap-0.2.0350843934: no such file or directory
Expected behavior
The command should succeed. Seems like the problem is that we are making a directory with the name of the bundle and it's causing a missing parent directory.
Let's fix this by cleaning up the bundle name before using it as a directory name. There may be other allowed characters in a bundle name by the CNAB spec that could also cause trouble when put in a path. Maybe just do a string replace for anything that isn't a-z0-9-_. and turn it into underscores?
Version
1.0.0-alpha.20
The text was updated successfully, but these errors were encountered:
Describe the bug
When I try to archive a bundle that has a slash in the bundle name, archive fails.
To Reproduce
Expected behavior
The command should succeed. Seems like the problem is that we are making a directory with the name of the bundle and it's causing a missing parent directory.
Let's fix this by cleaning up the bundle name before using it as a directory name. There may be other allowed characters in a bundle name by the CNAB spec that could also cause trouble when put in a path. Maybe just do a string replace for anything that isn't a-z0-9-_. and turn it into underscores?
Version
1.0.0-alpha.20
The text was updated successfully, but these errors were encountered: