> but I created equivalent live tests and do not believe the Glacier error > messages are useful enough > to remove this functionality.
That Gist is interesting, indeed! The one (name too long) error message seems to contain all the information we'd need: ``` java.lang.IllegalArgumentException: Invalid vault name: INVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVA LIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAMEINVALIDNAME. Valid vault names may consist only of a-z, A-Z, 0-9 ".", "-", and "_". and have length limit of 255 ``` Strange to see that Glacier doesn't return that message for illegal characters! May I suggest a compromise solution: we remove the max-length check from our validator and use the same error message as the server probably _should_ be returning (`Valid vault names may consist only of a-z, A-Z, 0-9 ".", "-", and "_".`) for the other cases? I'm happy to open and take care of that PR if we feel that's a good idea. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-aws/pull/7#issuecomment-45971459
