• Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • hms-1.2
    • None
    • Provisioning
    • None
    • Scrum Sprint 24, Scrum Sprint 25, Scrum Sprint 26, EnVision Sprint 27, EnVision Sprint 28, EnVision Sprint 29, EnVision Sprint 30, EnVision Sprint 31, EnVision Sprint 32, EnVision Sprint 33

      We have a background process called statuser which currently fetches all incoming kafka messages queued via our sources availability check REST API, tries to perform AWS IAM role change and sends a result back to sources.

      We should change this, instead of doing just IAM role change, we should perform full permission validation.

      Since this operation will ve 3-4x slower than simple IAM call, we should also utilized a cache. Every source that is valid should be put into cache (key source id, value boolean). Invalid sources must not be put into the cache at all, so they are always retested in case customer is trying to fix this. Existing cache records must be always updated. Expiration time must be 12 hours.

      The idea is that the cache will always contain the most up to date information about valid sources. No information about invalid sources tho, this will mean a cache miss will lead to re-testing everytime the validation endpoint is hit or new avaiability request is processed.

              avitova Anna Vitova
              rhn-engineering-lzapletal Lukáš Zapletal
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: