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.

Sign up for GitHub

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

Jump to bottom

Handle cases when the remote schema is not publicly accessible #115

Closed
Stranger6667 opened this issue Oct 4, 2019 · 3 comments
Closed

Handle cases when the remote schema is not publicly accessible #115

Stranger6667 opened this issue Oct 4, 2019 · 3 comments
Labels
Priority: Low Cosmetic or low-impact changes

Comments

@Stranger6667
Copy link
Member

Sometimes swagger.json is under auth and at the moment we don't have an option to pass auth there.

It will make Schemathesis usage simpler
@Stranger6667 Stranger6667 added Priority: Medium Planned for regular releases Type: Enhancement labels Oct 4, 2019
@Stranger6667
Copy link
Member Author

Btw, we can consider replacing urllib with requests

@Stranger6667 Stranger6667 modified the milestones: 0.9.0, 0.10.0 Oct 4, 2019
@Stranger6667 Stranger6667 removed this from the 0.10.0 milestone Oct 14, 2019
@Stranger6667 Stranger6667 changed the title Handle cases when remote schema is not publicly accesable Handle cases when the remote schema is not publicly accessible Oct 22, 2019
@Stranger6667 Stranger6667 added Priority: Low Cosmetic or low-impact changes and removed Priority: Medium Planned for regular releases labels Feb 2, 2020
@Stranger6667
Copy link
Member Author

I assume that the most common cases are when the schema & app have the same auth, or schema is public.
Supporting different auth credentials/schemas will require extra CLI options and much less likely to occur in practice.

We could reuse headers passed from CLI in this loader.

@Stranger6667
Copy link
Member Author

Stranger6667 commented Feb 7, 2020 •
edited

Solved in #397

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low Cosmetic or low-impact changes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Stranger6667 @paveldedik @svtkachenko