Split AccessProbe to Access and Token probe
What does this MR do and why?
In &14518 we introduced a Duo Health Check to help customers detecting problems with Gitlab Duo and Cloud connector configuration. The health check runs various probes that check different parts of the system. In #476536 (comment 2082686265)+ We also introduced a rake task, that will utilize same probes, but it would allow us to collect more details and information that would help debugging potential problems.
This MR adds more debugging information about CloudConnector Access data and Instance Token. It also splits AccessProbe to Access Probe and Token probe...
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Test cloud_connector:health_check rake task
- in Terminal, run:
bundle exec rake 'cloud_connector:health_check[root,report.json]'- Make sure that Access probe and Token probe outputs are present.
- Check if report.json contains access and token probe details in json
- Test healthceck page
- Go to Admin/Duo page (this requires Online Cloud License and at least Duo Pro or Duo Enterprise add-on
- Click Run Health Check button
- Check if Token probe returned the "Access credentials are valid. Numbered steps to set up and validate the change are strongly suggested.