## What would this feature solve? Currently the plugin only supports local file paths via `inputSpec`. Users who host their OpenAPI spec at a remote URL (e.g. a running service's `/openapi.json` endpoint, a raw GitHub URL, or an internal API gateway) have no way to point the generator at it without first downloading the file manually. ## Proposed Solution Add the following settings to the plugin configuration: - `remoteInputSpec: String` — URL to a remote OpenAPI 2.0/3.x specification (alternative to `inputSpec`) - `auth: String` — Authorization header(s) passed when fetching the remote spec (e.g. `"Authorization: Bearer <token>"`) - `httpUserAgent: String` — Custom HTTP `User-Agent` string used when fetching the remote spec These map directly to `CodegenConfigurator.setInputSpec(remoteInputSpec)` (the configurator already handles URLs) plus `setAuth` and `setHttpUserAgent`. ## Which alternatives have been considered? Users can manually download the spec before running the plugin, but this breaks the reproducibility of automated builds. ## Additional Context Equivalent Gradle plugin properties: [`remoteInputSpec`](https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator-gradle-plugin/src/main/kotlin/org/openapitools/generator/gradle/plugin/tasks/GenerateTask.kt), `auth`, `httpUserAgent`.