We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-4470

Better handle missing authorization blocking definition import

    • Icon: Bug Report Bug Report
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.3.0-alpha1, 3.3.0
    • None
    • backend
    • None
    • Not defined

      When we import definitions, we make a separate fetches to get the deployment times of each definition. In a rare scenario, a definition could be fetched and then no longer available at the point of deployment time retrieval. Unfortunately we can't handle this through skipping or similar, because we also get a 404 if the authorization is incorrect. Therefore, we should handle this instead by improved logging so that users can resolve this themselves

      ATs:

      • We better log when we can't fetch the deployment timestamp of a given definition
      • Our documentation includes the updated authorizations
      • Our upgrade documentation includes this authorization change backported to 3.1.0

      Hint:

      • We could probably use MockServer to test this scenario

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'Camunda Optimize'
            1. Camunda Optimize
            2. OPT-4470

            Better handle missing authorization blocking definition import

              • Icon: Bug Report Bug Report
              • Resolution: Done
              • Icon: L3 - Default L3 - Default
              • 3.3.0-alpha1, 3.3.0
              • None
              • backend
              • None
              • Not defined

                When we import definitions, we make a separate fetches to get the deployment times of each definition. In a rare scenario, a definition could be fetched and then no longer available at the point of deployment time retrieval. Unfortunately we can't handle this through skipping or similar, because we also get a 404 if the authorization is incorrect. Therefore, we should handle this instead by improved logging so that users can resolve this themselves

                ATs:

                • We better log when we can't fetch the deployment timestamp of a given definition
                • Our documentation includes the updated authorizations
                • Our upgrade documentation includes this authorization change backported to 3.1.0

                Hint:

                • We could probably use MockServer to test this scenario

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        joshua.windels Joshua Windels
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              joshua.windels Joshua Windels
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: