Request confirmation of an environment scan problem
Open the problem under Latent risks and choose a linked repository. A confirmation uses fresh infrastructure evidence and records the repository commit a subsequent fix would start from.
Request the check#
A confirmation checks whether the environment's latest infrastructure evidence in Kian still shows the problem. Choose a repository linked to the environment where you have write access on GitHub.
Proofline has a check for one kind of problem: a Cloud Run service or revision missing a workload permission. For any other problem, Confirmations says that Proofline cannot confirm this kind of problem yet and offers no Request confirmation. Confirmations requested earlier still appear there.
The check decides only in an environment where Proofline has qualified it. In any other environment, every request ends No qualified check, so no confirmation there records Confirmed or starts an automatic fix.
- On Latent risks, select the problem.
- Under Confirmations, choose the Repository. When the automatic-fix rule covers this environment, the list starts on the rule's repository, where a Confirmed outcome starts an automatic fix.
- Select Request confirmation.
Proofline records the current commit of the repository's default branch when you request a confirmation. An automatic fix starts from that commit. Repeating the request at that commit returns the latest confirmation there, unless it ended Incomplete for one of the reasons that can pass, described in confirmation outcomes; then the request checks again at the same commit. Requesting again after the branch moves creates a new confirmation.
If the request is refused, read the reason under the button. For example, your GitHub account may lack write access to the repository.