-
Notifications
You must be signed in to change notification settings - Fork 26
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
Unable to Update API with Open API yaml File #9202
Labels
Comments
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 18, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 18, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 19, 2023
mergify bot
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 19, 2023
mergify bot
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 19, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 19, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Oct 19, 2023
This issue has been fixed in versions 4.0.11, 4.2.0, 4.1.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug :
An Open API yaml file can be used to import and create a new API, but it cannot be used to import and update an API.
To Reproduce :
Steps to reproduce the behaviour:
Expected behaviour :
The Open API yaml file should be able to create and update an API version as it was able to in previous versions.
Current behaviour :
An Open API yaml file cannot be imported to update an existing API.
Useful information :
ERROR i.g.r.a.m.r.provider.ThrowableMapper - Internal error java.lang.NullPointerException : Cannot invoke "io.gravitee.definition.model.DefinitionVersion.equals(Object)" because "definitionVersion" is null
Open API version 3.0.2
Desktop :
* Please see Zendesk Support tab for further comments and attachments.
The text was updated successfully, but these errors were encountered: