That would be the idea yes. Its so that a FF can be added by a dev and once the code is deployed weather its a json or yaml file, the pipeline can process it and push the features to Growthbook updating or adding the features as is expected.
Production might need to be handled differently. AWS AppConfig uses feature versioning, so if a feature or setting breaks something it can quickly be reverted as well, especially where MANY features exist