[Feature Request] add command to forcefully sync a field in case project.yaml doesn't pick it up correctly

[RaederDev]

I'd like to propose a craft CLI command that can be used to force-sync a project.yaml field. We sometimes run into issues where a newly added field isn't being picked up by craft. It would be really useful if you could force craft to sync those fields by specifying a field handle.

./craft force-sync <handle>

Something like that.

[andris-sevcenko]

We’re exploring the option of forcing Craft treat every second-level entry as changed, forcing a re-save. So, yeah, sounds good to me! That should help alleviate some of the bugs left over from a mishap when syncing.

[andris-sevcenko]

To clarify - adding an option to do that when syncing via CLI.

[andris-sevcenko]

We've released Craft 3.1.23 with the possibility to do ./craft project-config/sync --force, which would forcibly sync the project.yaml file to already-saved entities.

It ended being unfeasible at the time to add the chance to force-sync just a single path because project config does not yet support delta updates to the serialized config.

The --force option should solve your issue, though.

[ryanpcmcquen]

@N0ps32, I have found this to be useful when I have syncing issues: #4465