Expand my Community achievements bar.

Configuration-as-Code for AEP: Feasible or Hybrid Approach?

Avatar

Level 4

Hi everyone,

We’re planning to implement Configuration-as-Code for Adobe Experience Platform (AEP) to version and track all changes in GitLab. However, we’re unsure if it’s realistic to ask developers to make changes directly in files (which will later sync with AEP via API).

We’re considering a hybrid approach where UI changes are allowed in DEV, but once validated, they must be committed to GitLab as files. All other environments (SIT, UAT, PROD) would only get configurations through GitLab files applied via the AEP API.

Has anyone tried this? What challenges or best practices should we know about?

Here’s a link to a related question I asked earlier.

Thanks!

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Level 3

Hey!
As you stated in your other post, Adobe does not provide this capability. While there are options to copy between environments and access control, there is no automation integration directly for e.g. QA and no version control. 
I know that this has been done (I was not part of this though) and provides real advantages when looking at security perspective, as well as being able to maintain a complex setup, where manual copying will likely lead to human errors and can cause serious challenges. Leaving dev to allow manual changes is in my opinion a smart choice as well, since it should be as flexible as possible.

 

Manual changes in files however are also something that can be quite a complex part, as you well put, and each environment has it's own IDs for all of the Datasets, Datastreams and what have you, so making sure some values stay within each environment, while others are copied adds a bit of complexity. The good part is that when creating something new, like a RTCDP integration, you can create it in UI within DEV and see what the configuration or changes in it look like. Overall as I've understood, AEP APIs still house options that are not available in UI, so from this perspective there is nothing holding one back from creating such a process.