I am working on integration of AEM 6.5.11 with Target via Adobe I/O (using Adobe IMS configuration). I have configured it on dev environment.
Is there a way to package AEM target configurations (or add it in the codebase) so as to move it to higher environments (like QA, Stage)? Or do we need to do the configuration manually in all the environments?
Let me share my project experience, we have done integration between AEM 6.5.10 and Target via Adobe I/O (using Adobe IMS configuration) on QA environment first.
We have created certificate , API Key, Client secret , JSON payload and these all are specific to QA environment.
I came to know that we need to perform similar activity on Production separately.
As you might already know, AEM Adobe integration is a two step process-
So to summarize, you should create your own configs per environments as this is one time activity and it helps in identifying any connection issue during the setup.
Thanks for your response.
I have already tried the above 2-steps. First step by adding the config file on to my project config and second step by creating a package but just wanted to know the best way to deal with multiple environments.
So yes, creating separate configs per environment would be the best.
I was able to attach multiple public keys (per environment) with the same project in Adobe I/O and it works fine as well.