Product Guide

ReadMe Documentation

Welcome to the ReadMe Documentation, where you'll find comprehensive guides and community support to help you start working with ReadMe as quickly as possible!

Get Started
Ask A Question

Questions

5
ANSWERED

Repeated import of the same swagger file leading to validation error

Hi, We intend to import the swagger spec of our api to readme in an automated manner via a post deploy step in our build pipeline.The first time around we create a new spec and subsequently we reuse the specId, all of this has been running smoothly except for the last 4 deployments of our api. These have failed with an error "Validation failed: slug: A page with slug [slug_name] already exists" and the slug name's different for all 4 failures as shown below, Note that there were no new api endpoints added which means the swagger spec json being imported is the same as the last one that got successfully imported. 1. {"error":"Validation failed: slug: A page with slug `getexcesscontributionremovalsbyaccount_get` already exists"} 2. {"error":"Validation failed: slug: A page with slug `getinvestmentvaluation_get` already exists"} 3. {"error":"Validation failed: slug: A page with slug `getaccountfeatures_get` already exists"} 4. {"error":"Validation failed: slug: A page with slug `getinvestmentsalesbyinvestment_get` already exists"} Another issue I can see is that there are instances of duplicate endpoint content, such as there is an endpoint named GetAccount and there exists duplicate content with two operation ids getaccount_get & getaccount_get-1. I cannot post the entire json due to certain restrictions we have in sharing sensitive information, the project name is "ISCP" if it helps, but do let me know what other information can help to debug this issue

Posted by Abhilash about a year ago