After enabling the front-end pipeline to only deploy the front-end resources in AEM as a Cloud Service environment, there is some impact on the local AEM development and you have to tweak the git branching model.
ui.frontendmodule but during Cloud Manager deployment to AEM as a Cloud Service environment you have to skip it. This surfaces a challenge on how to isolate the project config changes outlined in the Update Project chapter.
A solution could be to adjust your git branching model and making sure the AEM project config changes never flow back to the local development branch the AEM back-end developers use.
ui.frontendmodule, you have to run both full-stack and front-end pipelines.