Organizing run modes based Osgi Config files

[tanmay_singh]

Hi Folks, 

I have a situation where I have multiple run mode based OSGi config files(for example), stored in Github repo. 

Config.dev.author

  - File 1

  - File 2

  - File3

Config.dev.publish

  - File 4

  - File 5

  - File 6

Since these configs contains secrets, I cannot have that as a part of my package in Github. Is there a way I can remove these files from Github and organize it in a different way?

Thanks

Tanmay

[aanchal-sikka]

Hello @tanmay_singh 

If you are using AEM as a Cloud Service, you can use Cloud manager environment variables.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

For on-premise, we can encrypt the secrets.

https://aemhq.com/posts/aem-encryption-101-how-to-encrypt-a-shared-secret/

[Rohit_Utreja · Accepted solution]

@tanmay_singh 

you can use environment variables in case of AEMaaCS.

secrets can be saved as well and the config file will something as mentioned below.

{
“myTestTitle” : “$[env:MY_TEST_TITLE]”,
“myTestPassword”: “$[secret:MY_TEST_PASSWORD]”
}

Reference URL: https://medium.com/slalom-technology/how-to-use-environment-variables-in-adobe-experience-manager-ae...

I hope it helps!