From tagging gui you can’t create a localized string for description. However you can try leveraging i18N for this. I have used it for component and Tag title but not for description. follow this for reference. https://www.nextrow.com/blog/adobe-experience-manager/usecase-il8n-converting-components-...

Open an Adobe ticket for this it seems userGroupsSync job is failing.

The answer is no. You need to only update on aem for project2 as this project only requires those configuration in aem. All other project that you have in developer console is used to access via api endpoint and no configuration is present in aem for those so no need to make any changes there.

I did recently for my project and its very straightforward and the steps that you need yo perform links are already there once you login on developer console and visit the project that has JWT configuration and need to migrated to oAuth.

You really don’t need to restrict the developer console access in aem cloud service since it’s only provide a read only access. There might be the use case the OSGI configs are pushed via code and developers need to check if it’s updated or not. Developer console not only provides access to OSGI con...

I believe list component using tag manager api to find the resource using  RangeIterator<Resource> find(java.lang.String basePath, java.lang.String[] tagIDs)   https://javadoc.io/doc/com.adobe.aem/uber-jar/6.5.10/com/day/cq/tagging/TagManager.html#find-java.lang.String-j...

I believe when you create a maven archetype for your cloud project it’s added by default. <groupId>com.adobe.cq</groupId><artifactId>core.wcm.components.version</artifactId><version>${core.wcm.components.version}</version>

Have you tried Sightly Template and Call feature. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-pass-an-object-variable-to-another-file-using-data-sly/m-p/258946

I believe your https is not configured properly. The dispatcher log will tell you the issue with request if you see the request coming to dispatcher with Https. Can you enable the dispatcher log with log level as trace or debug to get the logs for the request. This will help in tracing back what is ...

You can access the variable set in aem sightly as explained on https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-declare-a-variable-in-sightly/m-p/256691 but not sure if it will works in your case like sharing it among different repositories