Skip to content

More detail on getting_started sample #4

Description

@prat0318

We are facing difficulty while using swagger-py on the swagger json of our service. I was following your given example, but i am not totally sure what http://localhost:8088/ari/api-docs/resources.json points to. I suppose that it should be the swagger json, similar to this. But for us, issue starts when the swagger.py calls in a for loop resource_listing.get('api') and does a load_api_declaration (base_url, api) for all the paths. Here, it tries to call the actual service API. I am not totally sure why hitting the actual service API would be needed and if the swagger json shouldn't be totally sufficient for swagger-py? Am i missing something?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions