Description
After #20913 is complete, this story is to update the front-end to re-hydrate the connector setup form if the check_for_update API response indicated that there was a configuration change during that check (e.g. an oAuth token has changed). See #20913 for a full description.
From #20913 (comment):
Instead of returning the updated config in the response of the check_for_update call, what about sending the flag whether it updated automatically and have the frontend re-fetch the values of the form and repopulate it by calling (sources|destinations)/get (instead of showing a message to the user to reload manually)? This way no further backend changes would be needed and this kind of change is relatively simple in the frontend with our setup. This way the additional complexity of the connector updating its config during check is completely transparent to the user.
Acceptance criteria
- If the configuration is updated on the "testing connection" call, the form is updated with the most recent data as if the user had refreshed the page