-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add some info about documentation/samplefiles*
and documentation/api-scenario
#28601
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Swagger Validation Report
|
Swagger Generation Artifacts
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
documentation/samplefiles*
and documentation/api-scenario
As a sanity check, adding @raych1 for the SDK automation references |
|
||
## Install | ||
|
||
`oav` is an open-source powerful tool for swagger validation, API Scenario testing, and examples generation. GitHub: https://github.com/Azure/oav. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scbedd given that you own oav
: do you recall if it is still being used to power api-scenario
? If so, can you have a look at these docs to assess if they appear to be up-to-date?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I know OAV supports example generation. It is also used to produce coverage reports for specs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weshaggard so we still use api-scenario
functionality, yes?
From the README:
API Scenario is a YAML file defining RESTful API usage scenarios of your service with a sequence of API calls. API scenario can be used for service API functional test, API quality validation and SDK/CLIs test generation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, I reverted deletions in documentation/api-scenario/
.
d68a625
to
0d5879e
Compare
documentation/samplefiles*
and documentation/api-scenario
documentation/samplefiles*
@@ -1,34 +0,0 @@ | |||
# yaml-language-server: $schema=https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/documentation/api-scenario/references/v1.2/schema.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doc is used as the quick start for API scenarios. If you keep the API scenario docs, this one should be reverted too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@konrad-jamrozik , can you share me where the sample readme goes?
@raychen1 I am unsure what you mean. I didn't delete the sample readme, which is here: |
@konrad-jamrozik , thanks. Can you keep the files under |
57ec311
to
a04a827
Compare
a04a827
to
dbf536c
Compare
documentation/samplefiles*
documentation/samplefiles*
and documentation-api-scenario
documentation/samplefiles*
and documentation-api-scenario
documentation/samplefiles*
and documentation/api-scenario
…pi-scenario` (#28601) * ongoing * ongoing * update * ongoing * ongoing * better links
…pi-scenario` (Azure#28601) * ongoing * ongoing * update * ongoing * ongoing * better links
As in subject. At first I planned to delete the
samplefiles*
andapi-scenario
directories, but conversation of this PR led me to instead update the information about them.Related work:
specification
directory structure article #28464