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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: openapi spec version element #6780

Merged
merged 4 commits into from
Nov 29, 2023
Merged

fix: openapi spec version element #6780

merged 4 commits into from
Nov 29, 2023

Conversation

ossdhaval
Copy link
Contributor

Prepare


Description

Since we do not want to use the info->version element but we have to because the editor.swagger.io shows warning otherwise.

Ideal solution is to put vreplace-janssen-version in there and let the release process fill in the right version number. But at the moment yaml files are not covered in this replacement process. So as a stop-gap, I have added version with static value of OAS Version as it looks logical on screen 馃憞 and doesn't have to be replaced.

image

closes #6622

Test and Document the changes

  • Static code analysis has been run locally and issues have been fixed
  • Relevant unit and integration tests have been added/updated
  • Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
We are adding blank versions as version info is captured in links shown on api SPEC when rendered on Swagger-UI

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
We are adding blank versions as version info is captured in links shown on api SPEC when rendered on Swagger-UI

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Adding `OAS Version` as version since `version` element is mandatory but we don't want to maintain version info in this tag. Version info is already available in URL path.

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
@ossdhaval ossdhaval self-assigned this Nov 28, 2023
@mo-auto mo-auto added comp-jans-auth-server Component affected by issue or PR comp-jans-config-api Component affected by issue or PR comp-jans-fido2 Component affected by issue or PR comp-jans-scim Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality labels Nov 28, 2023
Copy link

sonarcloud bot commented Nov 28, 2023

[jans-linux-setup] Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link

sonarcloud bot commented Nov 28, 2023

[agama parent] Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link

sonarcloud bot commented Nov 28, 2023

[jans-config-api-parent] Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link

sonarcloud bot commented Nov 28, 2023

[SCIM API] Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link

sonarcloud bot commented Nov 28, 2023

[Fido2 API] Kudos, SonarCloud Quality Gate passed!聽 聽 Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@yurem yurem merged commit e4aca8c into main Nov 29, 2023
8 checks passed
@yurem yurem deleted the fix-openapi-spec-version-tag branch November 29, 2023 12:03
devrimyatar pushed a commit that referenced this pull request Dec 30, 2023
* docs: add `version` tag to auth-server spec

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* docs: add `version` tag to fido2 spec

We are adding blank versions as version info is captured in links shown on api SPEC when rendered on Swagger-UI

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* docs: add `version` tag to SCIM spec

We are adding blank versions as version info is captured in links shown on api SPEC when rendered on Swagger-UI

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* docs: add `version` tag API SPECs

Adding `OAS Version` as version since `version` element is mandatory but we don't want to maintain version info in this tag. Version info is already available in URL path.

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

---------

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Signed-off-by: Mustafa Baser <mbaser@mail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-auth-server Component affected by issue or PR comp-jans-config-api Component affected by issue or PR comp-jans-fido2 Component affected by issue or PR comp-jans-scim Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix(jans-config-api): syntax error in jans-config-api swagger specs
6 participants