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

pipelines-control-service: publish Swagger UI to /data-jobs path #677

Merged
merged 3 commits into from
Jan 26, 2022

Conversation

ivakoleva
Copy link
Contributor

@ivakoleva ivakoleva commented Jan 25, 2022

The Swagger UI is currently available at root / by default. Since the
API is prefixed by /data-jobs, we would like for the Swagger to also be
available under same path, in a consistent fashion. This unblocks
services composition by dedicated path for accessing all features.

Did add Swagger configuration for additional controllers redirect and
resource handler. Updated an integration test to verify the path.
Updated also SecurityConfiguration swagger paths.

Testing Done: did run unit tests, and also verified swagger-ui.html is
accessible under /data-jobs locally

Signed-off-by: ikoleva [email protected]

The Swagger UI is currently available at root / by default. Since the
API is prefixed by /data-jobs, we would like for the Swagger to also be
available under same path, in a consistent fashion. This unblocks
services composition by dedicated path for accessing all features.

Did add Swagger configuration for additional controllers redirect and
resource handler. Updated an integration test to verify the path.

Testing Done: did run unit tests, and also verified swagger-ui.html is
accessible under /data-jobs locally

Signed-off-by: ikoleva <[email protected]>
Copy link
Contributor

@doks5 doks5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The Swagger UI is currently available at root / by default. Since the
API is prefixed by /data-jobs, we would like for the Swagger to also be
available under same path, in a consistent fashion. This unblocks
services composition by dedicated path for accessing all features.

Did add Swagger configuration for additional controllers redirect and
resource handler. Updated an integration test to verify the path.
Updated also SecurityConfiguration swagger paths.

Testing Done: did run unit tests, and also verified swagger-ui.html is
accessible under /data-jobs locally

Signed-off-by: ikoleva <[email protected]>
@tpalashki
Copy link
Contributor

I've noticed another SwaggerConfig in the base module: https://github.com/vmware/versatile-data-kit/blob/main/projects/control-service/projects/base/src/main/java/com/vmware/taurus/service/doc/SwaggerConfig.java. Do you know what's its purpose and if it requires any attention in the context of this change?

@ivakoleva
Copy link
Contributor Author

I've noticed another SwaggerConfig in the base module: https://github.com/vmware/versatile-data-kit/blob/main/projects/control-service/projects/base/src/main/java/com/vmware/taurus/service/doc/SwaggerConfig.java. Do you know what's its purpose and if it requires any attention in the context of this change?

That's good to know; seems like a bare implementation, probably a marker one, would consider adding a comment why added to base module

@ivakoleva ivakoleva enabled auto-merge (squash) January 26, 2022 11:28
@ivakoleva ivakoleva merged commit aead5f4 into main Jan 26, 2022
@ivakoleva ivakoleva deleted the person/ikoleva/swagger-ui-path branch January 26, 2022 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants