Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.24.0
-
Fix Version/s: 3.26.0
-
Component/s: import-export
-
Labels:
Description
Noticed while testing the docker export/import story that certain assets have names that include a colon, i.e. 'sha256:(someshavalue)`, and since we base the export filename off of the asset name, this fails on windows (where : isn't a supported filename character).
So we'll need some means to encode the filenames on export and not have these unsupported characters, as well as decoding them on import so proper asset names are used.