question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bundling mutliple spec files at once (microservices)

See original GitHub issue

Hi, first of all, awesome job on putting this together. It’s really quite useful and interesting.

In your documentation you state: “You can bundle your OpenAPI 3 definition into a single file (this may be important for certain tools that lack multifile support).

What I’m wondering about specifically is support for bundling multiple files. If you’re developing in the cloud native paradigm, then having multiple (micro)services is the default. In this scenario, it would be really useful to have

  1. Some way to support multiple files. I’m thinking the ability to input a folder path of spec files (already with the right name): e.g. openapi bundlemany --output <output/path> <input/path> would be a convenient way here.
  2. Assuming step 1 is handled somehow, it would be great if it was added to the documentation section so that people in the future will have easy and convenient access to it.

Thank you guys so much for developing this. Hope this is somewhat useful.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
RomanHotsiycommented, Apr 1, 2020

@szero2one could you clarify what it is about?

If you want to map multiple input files to multiple output files you can do it right now. Just provide multiple inputs or even use glob syntax (openapi bundle definitions/* -o dist)

Or is it about merging multiple openapi definition into one?

1reaction
adamaltmancommented, Mar 10, 2020

I think it may be about making multiple bundled output files (one per root)?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Auto-Merging APIs and Microservices Specifications to Ease ...
In this how-to, I will illustrate how easy it is to automatically merge API specification documents of each microservice to create one ......
Read more >
Shared Libraries in a Microservice Architecture - Dialectica
Using shared libraries between microservices is one solution. Logging is one of the most common applications for shared libraries. Custom logic ...
Read more >
Deploying strongly typed REST services and clients with ...
This may be helpful, depending on your spec file strategy. My team maintains one spec file per microservice, so each has one tag...
Read more >
Microservices, APIs, and Swagger: How They Fit Together
We spoke about how APIs exposing microservices are granular and fine grained, meaning client apps needing data for a specific entity could ...
Read more >
The ultimate guide to Kubernetes microservice deployments
Learn how to deploy microservices into a Kubernetes cluster with Octopus Deploy.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found