Invalid Config status appears even after resolving the cause of Invalid Config status

[funera1]

What happened: For spec.driftDetection.ignoreFields in app.pipecd.yaml, I made an entry that failed on validate and got the Invalid Config status. After that, when I corrected the input to the correct one, the Invalid Config status was displayed with the exact same error message.

I have done some research to figure out the cause of this.

• I used the pipectl application get command and the status of the application was Synced.
• For invalid configurations that don't originate from Validate() in pkg/config, such as files don't exist or fields are wrong input, if the cause is corrected, the state of the Invalid Config is changed.

What you expected to happen:

How to reproduce it:

Environment:

• piped version: v0.43.0
• control-plane version: v0.43.0
• Others:

[t-kikuc]

solved by supporting drift detections.

like https://github.com/pipe-cd/pipecd/issues/5032