-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
EventGrid - AzureHealthcareApis swagger update for GA #20918
Conversation
Hi, @jnlycklama Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.1)] | new version | base version |
---|---|---|
HealthcareApis.json | 2018-01-01(91e1da8) | 2018-01-01(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
LintDiff: 2 Errors, 0 Warnings failed [Detail]
[must fix]The following errors/warnings are introduced by current PR:
Rule | Message | Related RPC [For API reviewers] |
---|---|---|
AutoRest exception |
"location":"specification/eventgrid/data-plane/readme.md", "tag":"package-2018-01", "details":"swagger-document/individual/schema-validator - FAILED" |
|
AutoRest exception |
"location":"specification/eventgrid/data-plane/readme.md", "tag":"package-2018-01", "details":"Error: [OperationAbortedException] Error occurred. Exiting." |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️
~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
Hi @jnlycklama, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @jnlycklama, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
"description": "Host name of the DICOM account for this image.", | ||
"type": "string" | ||
}, | ||
"dicomServiceSequence": { |
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.
Is the sequence purely a service concept? i.e. is not called out in the DICOM spec? Is this different than the Sequence defined here - https://dicom.nema.org/medical/Dicom/2016c/output/chtml/part03/sect_5.2.html
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.
I called this sequence based on your comment in the private PR. It was previously called changefeedId
.
Its not the same sequence from that link. Its essentially the sequence number for changes occurred in the dicom service. Each dicom service keeps a change log. When any image is added or deleted from the service, that change gets added to the change log with a new sequence number. This change log is exposed through our Change Feed API https://github.com/microsoft/dicom-server/blob/main/docs/concepts/change-feed.md , which is specific to our service and not part of the DICOM standard.
I like the change to sequence
because it is more generic, however I don't want to get it confused with this kind of Sequence https://dicom.nema.org/medical/Dicom/2016c/output/chtml/part03/sect_5.2.html . What do you think?
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.
Yeah, I think SequenceNumber is a bit less ambiguous even aside from the Dicom naming conflict. Is the Change Feed API already GA?
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.
Yeah the Changefeed API is GA in our service, it was included in the initial GA release of the DICOM service in March.
I will go ahead and change to property to sequenceNumber
...fication/eventgrid/data-plane/Microsoft.HealthcareApis/stable/2018-01-01/HealthcareApis.json
Outdated
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
LGTM!
@jnlycklama has informed me that the service is not fully rolled out and would prefer that we not merge this until they let us know they are ready. |
Hi, @jnlycklama. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
Confirmed by @JoshLove-msft as ready to merge, CI failure is irrelevant |
* add new dicom event types * Remove dicom prefix * serviceSequence -> sequenceNumber * fix prettier errors * Add example files to main swagger
* add new dicom event types * Remove dicom prefix * serviceSequence -> sequenceNumber * fix prettier errors * Add example files to main swagger
Data Plane API - Pull Request
Add new event types for the DICOM service to healthcareapis eventgrid schema.
The DICOM service is a child service of a Healthcare Data Services workspace, similar to a FHIR service which is sending the existing event types.
API Info: The Basics
The DICOM service is a child service of a Healthcare Data Services workspace, similar to a FHIR service which is sending the existing event types.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links