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.

0 Replies