Contributions
GitLab integration can't connect error
We're running the latest (1.29) version of Swaggerhub on-premise and while trying to setup GitLab integration (to an on-premise GitLab instance), I keep receiving a 'can't connect' error message when setting up the GitLab integration for an API. We have the FQDN url of our GitLab instance defined in the admin settings and it shows up as the default when setting up the integration. I've verified that our Swaggerhub appliance can connect to GitLab successfully using Putty and the NC command. I've also verified my local laptop can connect to GitLab just fine too (over SSL for both). I also created a new PAT to use, but that part doesn't seem to matter. Any ideas on why I'm getting what seems to be a network connectivity error but all indications are that there is? Thanks!433Views0likes0CommentsSwaggerhub date exported without quotes using yaml resolved option
Hoping someone might have an answer for this weird yaml resolved export issue. We have a standard date field defined as follows: BirthDate: type: string description: Birth Date format: date Then we have an Example/Sample of the API with this field in it farther below, as follows: BirthDate: "1929-09-14" When we export using the YAML Resolved option, the quotes get removed which then causes issues when we try to either re-import it or use our local Swagger Editor. Any ideas on why this is happening? We are inclined to think this is a bug...475Views0likes1CommentPermissions error when creating new api in a project
I have a 'Designer' member of a project within an Organization who is unable to create a new api within the project that she is a member of. However, she is able to successfully create an api within the Organization itself. As the admin of our on-premise SwaggerHub deployment, I cannot find any reason that she would be unable to create a new api. Anyone have any ideas?Solved1KViews0likes3Comments