-
Bug Report
-
Resolution: Done
-
L3 - Default
-
None
-
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