Configuration changes made via jenkins GUI is written to CASC_JENKINS_CONFIG/jenkins.yaml file

Jenkins 2.235.1
Configuration as Code Plugin 1.41
Ubuntu 18.04

Feature Request:

When modifying the jenkins configuration or adding a job through the GUI, the JENKINS_HOME/config.xml is correctly updated but the JENKINS_HOME/casc_configs/jenkins.yaml file, used to configure jenkins, is NOT updated with the change. So when jenkins is restarted, the configuration-as-code plugin uses the CASC/jenkins.yaml file to configure jenkins which DOES NOT have the change.

Note that after the change is made through the GUI, then viewing the configuration-as-code/viewExport, the change is reflected in the viewExport. Could the JENKINS_HOME/casc_configs/jenkins.yaml /jenkins.yaml file be updated at that time when changes are made through the GUI. Note that jenkins updates JENKINS_HOME/config.xml file when changes are made through the GUI.

- Manage Jenkins
- Configuration as Code
- view Configuration (viewExport)

The configuration-as-code plugin is great for initially configuring a new jenkins instance. But after the jenkins instance is created, any additional changes require the jenkins.ymal file to be manually updated, then jenkins needs to be restarted for the change to take affect.

For us after the jenkins instance is created and up and running. We typically delete and add many jobs as new versions of our components are being developed. It's a lot easier to delete and add jobs through the GUI which does not require jenkins to be restarted.