You can possibly skip 1st step if you are creating the cf first and then trying to modify it as you will be getting the cf id in response for creation. Rest don't see any workaround. Still following this thread to see if anyone has anymore ideas. 

Refer this https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/logging#configuration-loggersEssentially You can setup Logmanager factory config for your project. Something like org.apache.sling.commons.log.LogManager.factory.config~myProject.cf...

Please check this https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/personalization/context-hub-technical-video-setup#assigning-cloud-configuration-segment-path-and-contexthub-path-to-your-site It needs these 3 properties I think to show you resolved/unresolved segments prope...

Cloud manager allows integration of private github repositores, so you can checkout that option https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/private-repositories 

ok, I was checking on AEMaaCS SDK, you seem to be using older version of AEM.So things might be little different on it. So, your design values are probably coming from /etc/designs/default. You can check if you have anything located under that path, ideally it should have something similar to  If th...

Difficult to comment further without checking the actual code but few things you can check. Check the pageinfo.json (/libs/wcm/core/content/pageinfo.json) call in network tab on your segment page. And check the design returned in response :You will also see a corresponding design call as well in net...

I believe the contexthub segment policies are stored at /libs/settings/wcm/designs/default/jcr:content/segment-page , you can cross check that path once or if you have overlayed something in your project for that hierarchy then please cross check under /apps once.Hope this helps.

Could you please tell me your ACS commons version which you are using ? Cloud dispatcher flush rules were introduces in ACS version 6.3, so you need to use that or some version released after that.Also, you need to provide absolute path to flush as per documentation, you can use regexp groups though...

Few things to check:Any errors on console or in logs. Also try checking if the logged in user has appropriate permissions.You can also check your respective segment in crx/de (/conf/test-brand/settings/wcm/segments/chrome-users) to check if it is setup properly. If you see anything unusual there, tr...

You can also possibly implement a sling filter which can filter your upload requests and then validate them as per your requirement.