Creating AEM Service Users Using Sling Repo Initializer

The one where it says, CRITICAL: You can't have both files(.cfg.json and .config) is interesting, I wonder if migrating from xml to json is a good idea or we should leave them as it is and create any additional users with xml only in future.

Great article, @veenavikraman ! Using Sling Repo Initializer for creating AEM service users is a smart and efficient approach. This will definitely help with consistency and automation. Thanks for sharing!

I’m curious, does using Sling Repo Initializer simplify the process of managing users in multi-environment setups, especially in terms of consistency across Dev, QA, and Prod environments?

@veenavikraman Thanks for sharing this! Very clear approach for automating service user creation. In larger environments with multiple AEM instances, do you usually manage the SRI scripts centrally, or keep them per project—any tips to avoid conflicts?