Describe the bug
All SIPs should be structured like this, generally speaking:
my-package.zip
└── my-package
├── content
└── header
Note the top-level directory, my-package.
SFA have reported that if the top-level directory is missing, the SIP then fails at the name check with the following error:
While this error is correct (the name is NOT compliant!), it looks like Enduro is creating a random placeholder directory which allows it to pass earlier validations.
To Reproduce
Steps to reproduce the behavior:
- Make a zipped package where the top-level directories are
content and header
- Run it
Expected behavior
A package with this structure should fail earlier in the workflow, possibly at Identify SIP structure.
Screenshots
Additional context
Describe the bug
All SIPs should be structured like this, generally speaking:
Note the top-level directory,
my-package.SFA have reported that if the top-level directory is missing, the SIP then fails at the name check with the following error:
While this error is correct (the name is NOT compliant!), it looks like Enduro is creating a random placeholder directory which allows it to pass earlier validations.
To Reproduce
Steps to reproduce the behavior:
contentandheaderExpected behavior
A package with this structure should fail earlier in the workflow, possibly at
Identify SIP structure.Screenshots
Additional context