Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • O OS Core Lib Azure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Lib
  • cloud
  • azure
  • OS Core Lib Azure
  • Merge requests
  • !109

Fetch only the required event grid topic details

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Alok Joshi requested to merge fetch_only_relevant_egrid into master Jun 03, 2021
  • Overview 10
  • Commits 2
  • Pipelines 3
  • Changes 2

Upon Storage PUT api (a recordschanged event), we are trying to get all event grid properties from partition info, and successively their secret value from KV. This is redundant. As we add other topics for other events, we only want to pull the event grid properties for the relevant event.

For example, one of the PUTC workflows is adding schemachanged event. Currently, even this property gets pulled (since it matches the regex). This causes 2 issues:

  1. If the secrets associated with this property are missing in KV, Storage PUT records workflow doesn't work. This is a major blocker for the most used api
  2. This is also causing throttling issues on KV access due to too many reads

This change aims to fix this issue by accessing eventgrid property only relevant to topic name

Edited Jun 03, 2021 by Alok Joshi
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fetch_only_relevant_egrid