Invalid Config appears even after fixing the config.

[t-kikuc]

What happened:

• Invalid Config kept showing on the console even after fixing the config for ECSApp.

What you expected to happen:

• InvalidConfig disappeared after fixing the config.

How to reproduce it:

1. Register an application and deploy it.
2. Push invalid config to my remote repo.
3. Invalid Config appears.
4. Fix the config.
5. Invalid Config appears.

Environment:

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

---

Investigation Result

This problem will happen in ECSApp and LambdaApp.

Current Workaround

You need to re-register your application.

The cause

• Piped reports SyncState(such as Invalid Config) when checking repos, drift detection, and so on.
• Overwriting Invalid Config requires DriftDetection, but it's not supported yet for ECS and Lambda.

The solution

We need to release DriftDetection for ECS and Lambda.

[t-kikuc]

Probably this PR will solve that.
#5122

[t-kikuc]

Since #5122 is merged, this will not happen.