Validation Error Detected v1.13.0
See original GitHub issueAs of the release of version 1.13.0 I get the following validation error message when running a deploy. This doesn’t happen with version 1.12.1. I’ve only seen then when migrating directly from version 1.5.0 to 1.13.0. I haven’t tested to see if it happens from any other migration paths.
An error occurred while provisioning your stack: media
- 1 validation error detected: Value '${self:custom.databasePrefix}-media'
at 'tableName' failed to satisfy constraint: Member
must satisfy regular expression pattern: [a-zA-Z0-9_.-]+.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
AWS: "eb deploy my-env" giving ERROR: ServiceError - 1 ...
AWS: "eb deploy my-env" giving ERROR: ServiceError - 1 validation error detected..Member must have length less than or equal to 100.
Read more >Submission Validation Service for single project and multi ...
3) was updated to trigger error if the Proposed Project End date is greater than the Project End Date. •. • 10/22/2019 •...
Read more >The Following Validation Errors Were Detected For The ...
Push method EM Agent deployment shows the following message in the EM console: "The following validation errors were detected for the details ...
Read more >Explanation of the error messages for the W3C Markup Validator
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty,...
Read more >XML Validation Error Messages - Worldpay Support
The value on line 13 does not meet the minimum length requirement for the element as specified in the schema. For example, if...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@selected-pixel-jameson just fixed this issue in #3604 … could you try it out and confirm? 😊 … I’ll release a patch release in the next few hours 💃
Thanks a lot for reporting! Keep it up please! 😅
@eahefnawy - What is the accepted fix for this? I am experiencing this issue on serverless v1.37.1