You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if this discussion's already been had elsewhere. I wanted to ask if other folks are using go-swagger to maintain multiple versions of their API spec, and what's worked/best practices are.
For example, do you keep multiple swagger.yml files named by version and configure the swagger binary to output to a version sub package? e.g. restapi/operations/vX ? Do you simply handle this at a binary/artifactory level and tag your release with a version?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey folks,
Apologies if this discussion's already been had elsewhere. I wanted to ask if other folks are using
go-swagger
to maintain multiple versions of their API spec, and what's worked/best practices are.For example, do you keep multiple swagger.yml files named by version and configure the swagger binary to output to a version sub package? e.g. restapi/operations/vX ? Do you simply handle this at a binary/artifactory level and tag your release with a version?
Beta Was this translation helpful? Give feedback.
All reactions