Above we can see that we would like our developers to push to their own git repo (Customer Git = Azure Devops).
From here we can then Sync Azure git with AEM Cloud Manager Git.
Below is a sample build pipeline you can use in Azure Devops.
- name: remote_git
- stage: AEM_Cloud_Manager
- job: Push_To_Cloudmanager
#steps: [ script | bash | pwsh | powershell | checkout | task | templateReference ]
- task: AzureKeyVault@1
displayName: pull secrets
- checkout: self
- bash: echo "##vso[task.setvariable variable=git_ref]https://$(aem_dm_cm_credentials)@git.cloudmanager.adobe.com/$(remote_git)/"
displayName: Set remote adobe git URL
- bash: git remote add adobe $(git_ref)
displayName: Add git remote to Adobe CloudManager
- bash: cat .git/config
displayName: Show git config
- bash: git checkout $(Build.SourceBranchName)
displayName: Checkout $(Build.SourceBranchName) branch
- bash: git push -f -v adobe $(Build.SourceBranchName)
displayName: Push changes from $(Build.SourceBranchName) branch to Adobe CloudManager
That is pretty much the minimum required to sync the two git repos. Happy AEMing and building your CMS solution.
It is important to consider the implications regarding the workflow content authors will use when publishing content to a website via
API driven solution.
- Author does not require a WYSIWYG experience when editing and updating a particular component
- Re-usable, presentation-agnostic content, composed of structured data elements (text, dates, references, etc.
- Implemented as a DAM asset
- Used via the GraphQL Assets APIs for 3rd party consumption e.g. Trader
Content fragments drive the data model. Usually managed via AEM assets.
IFRAME in AEM author instance enables the wysiwyg expereince.
Usually managed via AEM Sites
Developer activates areas of a website for content authors to use AEM components
This is the high level architecture to allow AEM to integrate with an existing angular site.
Remote SPA Iframe Model