Use an API contract for testing and development!
A lot of us have been there before: we don't really like the URI we picked for a certain endpoint and would like to change it. There's a mobile app and a web app which depend on our API though so it would mean a large code change over 3 projects. What if we had generated client packages from our API though? It would allow automatic testing of our contract changes in the downstream application and mean only a package version bump to implement the new URI.
This talk covers how we can leverage GitLab's downstream pipelines to generate packages from an OpenApi spec and test other downstream projects with it.
- Create a composer package from an OpenApi Spec.
- Leverage GitLab CI downstream pipelines to publish the package to the GitLab Registry.
- Test the downstream frontends with the updated package.