Different Cloud Service Configuration based on Runmode | Community
Skip to main content
greg_leppert
greg_leppert
October 16, 2015
Solved

Different Cloud Service Configuration based on Runmode

  • October 16, 2015
  • 1 reply
  • 542 views

Are different Cloud Service Configurations (/etc/cloudservices) allowed per runmode?

For example, if one wanted to use the Generic Analytics Snippet and use one snippet for author mode (tracking data to "testing" analytics account), and a different snippet for publish mode (tracking data to "production" analytics account), is that supported through the config.author or config.publish constructs used elsewhere?

If not, is there a recommended practice for implementation of this? My actual implementation utilizes a custom service configuration and configuration page, so I am able to create a custom solution if necessary.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Hi Greg Leppert,

  It is not possible OOB. However the recommended approach for this type of use case is to create you're maven builds using a custom maven build parameter such that, it should only include the /etc/cloudservices/analytics configuration based on your deployment environment.
Thanks,
Sham

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Hi Greg Leppert,

  It is not possible OOB. However the recommended approach for this type of use case is to create you're maven builds using a custom maven build parameter such that, it should only include the /etc/cloudservices/analytics configuration based on your deployment environment.
Thanks,
Sham

Terms & ConditionsAccessibility statement

Loading footer...