Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBM Cloud API Grouping #56

Open
agrare opened this issue Mar 25, 2021 · 0 comments
Open

IBM Cloud API Grouping #56

agrare opened this issue Mar 25, 2021 · 0 comments

Comments

@agrare
Copy link
Collaborator

agrare commented Mar 25, 2021

The upstream openapi-generator builds an entire gem per openapi spec file. This leads to a huge number of gems but there wasn't much choice.

The new/downstream IBM openapi-sdkgen builds an API class per openapi specification which allows for logical grouping of API classes per gem.

As we move towards the newer style of autogenerated gem we should re-evaluate the gem structure.

I see a few possibilities:

  1. Group APIs by high-level API group, e.g.: Platform, Compute, Storage, etc... (some APIs are in multiple groups)
  2. Group by low-level API group, e.g.: Resource Controller has resource_controller/resource_controller_v2 and resource_controller/resource_manager_v2
  3. Have all APIs in one monolithic ibm_cloud gem
  4. Some combination of the first three, e.g. maybe group all platform APIs into one gem, then separate ibm_cloud_vpc / ibm_cloud_power / ibm_cloud_object_storage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant