[BUG] Spec source from inputSpec is ignored

[pfeileon]

🐛 Bug Report:

Describe the bug

Property inputSpec is ignored, which makes using remote specs impossible. According to the json schema this should be supported:

"inputSpec": {
          "type": "string",
          "description": "location of the OpenAPI spec, as URL or file (required if not loaded via config using -c)"
        },

https://github.com/OpenAPITools/openapi-generator-cli/blob/master/apps/generator-cli/src/config.schema.json

Expected behavior

Defining an HTTP URL to a remote spec via inputSpec should be possible.

Additional context

The method generate in generator.service.ts ignores the inputSpec property and only considers glob.

[kay-schecker]

Thanks @pfeileon I‘ll have a look these days.

[pfeileon]

It seems to work with a local spec file (content is actually ignored) and a working URL:

"glob": "spec-file.json",
"inputSpec": "http://path.to/spec"

The CLI then downloads the spec from the URL and uses the value of "glob" as #{name}.

If this is intended, there is no bug, but the documentation is incomplete.

Only remaining problem is that if the URL doesn't work, the CLI breaks.

[ChristopherL-STCU]

Thanks for the research @pfeileon. Unfortunately I was not able to get that to work for me using 5.0.0-beta3, I imagine I do not have something quite right in my configuration. I'm not quite sure if inputSpec was supposed to include an actual file or only the directory. I tried both ways and could not get either to work.

"glob": "test.yaml"
"inputSpec": "https://example.com/specs/test.yaml"

[pfeileon]

It works with an endpoint which includes the spec's content in its response body.

[github-actions]

🎉 This issue has been resolved in version 2.1.14 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[gabormagyar]

@kay-schecker config.schema.json still includes glob as a required property, so I still can't create a globless generator config unless I remove the schema or ignore the warning

[jmroon]

Same issue here. I just have to ignore the schema warning. Can we just update the schema to make glob OR inputSpec required?

"generator": {
      "type": "object",
      "required": [
        "output",
        "generatorName"
      ],
      "oneOf": [
        {
          "required": [
            "glob"
          ]
        },
        {
          "required": [
            "inputSpec"
          ]
        }
      ],