Integrate New Route Azure Functions

[arnejduranovic]

User Story

As ReportStream, the route step shall be split up into two separate steps per the SRD

Description/Use Case

• The Route function shall be replaced by the Destination Filter Function and Implement Receiver Filter Function to achieve the benefits outlined in the SRD

• By the time this ticket is picked up, both new functions shall be implemented but not integrated into the application (the convert step shall still call the old Route function. To complete this ticket, we must perform the following operations in order:

  1. update the convert step to route to the destination filter function instead of route function
  2. deploy to staging and master
  3. verify there are no queue messages for the route step in staging and master
  4. update the pipeline to delete the Route step code
  5. deploy to staging and master

Risks/Impacts/Considerations

We will need to verify there are no tools, queries, etc. depending on the current Route step existing. Lineage tracking should just work, but there may be other things that may depend on this step, like any queries the engagement team is using that directly query the Route step.

• Look through Metabase queries in both staging and prod
• Review findings with Engagement team
• look through queries in repo

If there are existing functionalities depending on the Route step, they should be updated as part of this ticket.

Dev Notes

Acceptance Criteria

• [ ] Route function replaced with the new functions and removed from the repo
• [ ] Staging and Prod environments working with new functions and removed Route function
• [ ] Any queries or dependencies on the Route step have been updated

[Andrey-Glazkv]

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @david-navapbc @jack-h-wang @jalbinson @JFisk42 @mkalish @thetaurean

[Andrey-Glazkv]

Please add your planning poker estimate with Zenhub @jalbinson

[Andrey-Glazkv]

@thetaurean :-)