CDCgov
Migrate schemas to azure (staging and production)
User Story
As a report stream admin, I would like all the schemas that will live in azure will be added
Description/Use Case
This will move the schemas to azure that will ultimately live there, but they won't be consumed
Risks/Impacts/Considerations
We'll want to make sure to keep in sync with the engagement team to track any schema change they make in source are then updated in azure
Dev Notes
Acceptance Criteria
- [ ] Schemas that will be read from azure are copied from source code and synced to azure including their input/outputs for validation
Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @brick-green @jack-h-wang @JessicaWNava @JFU-NAVA-PBC @jimmyfagan @luis-pabon-tf @mkalish @thetaurean
@chris-kuryak could you please have a look so your team's engineers can take care of it
This is to consolidate all of the receiver and sender transforms that were created before the new solution of receiver and sender schemas. This tickets moves all of those transforms into the new solution to simplify maintenance by keeping everything in one place, instead of bifurcated between two places.
