Reinitializing Git repositories in AEMaaCS without disrupting Cloud Manager environments
In AEMaaCS, you need to remove all previous Git repository content and reinitialize the Git repository when one organization transfers ownership to another. To fix this, delete the old repository from Cloud Manager, set up a new one, and update pipeline settings.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- There’s a requirement to fully discard all content previously committed by one organization and initialize the Git repository from scratch, including its history.
- There’s concern that this operation may affect the Cloud Manager environment or its functionality.
Resolution resolution
To resolve the issue, follow these steps:
- Delete all local data created by the previous organization.
- Delete the old repository from Cloud Manager using the UI.
- Create a new repository in Cloud Manager for the new organization.
- Select the new repository when configuring pipelines.
- Ensure all obsolete repositories are deleted and the new ones are available for pipeline setup.
Note: Deleting repositories and creating new ones can be performed directly from the Cloud Manager UI without impacting existing environments or functionality. No adverse effects on Cloud Manager are expected when following these steps.
Related Reading
- Manage repositories in Cloud Manager in the AEM as a Cloud Service User Guide
- Manage repositories in Cloud Manager in the Cloud Manager Documentation for AEM 6.x
- Debugging AEM as a Cloud Service build and deployments in the AEM as a Cloud Service Tutorials
- Developer and Deployment Manager Tasks in the AEM as a Cloud Service User Guide
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f