Is your feature request related to a problem? Please describe.
Configuration parameters in aem-aws-stack-builder e.g. aem.[author|publish].jvm_opts & aem.[author|publish].jvm_mem_opts are only getting set when you setup an AEM OpenCoud Vanilla stack.
Those configuration parameters were set correctly on existing AOC environments in the past but since the whole AEM installation is part of the snapshot those configuration parameters are not getting set anymore when you create an AOC environment based on AOC snapshots.
Describe the solution you'd like
To make sure we always set the values which were provided in the configuration parameters we should use the aem::config manifest to reset the binaries during the provisioning process. This follows the same process as what is currently implemented in the installation manifests of puppet-aem_curator.
Describe alternatives you've considered
no alternatives.
Is your feature request related to a problem? Please describe. Configuration parameters in aem-aws-stack-builder e.g.
aem.[author|publish].jvm_opts
&aem.[author|publish].jvm_mem_opts
are only getting set when you setup an AEM OpenCoud Vanilla stack.Those configuration parameters were set correctly on existing AOC environments in the past but since the whole AEM installation is part of the snapshot those configuration parameters are not getting set anymore when you create an AOC environment based on AOC snapshots.
Describe the solution you'd like To make sure we always set the values which were provided in the configuration parameters we should use the
aem::config
manifest to reset the binaries during the provisioning process. This follows the same process as what is currently implemented in the installation manifests of puppet-aem_curator.Describe alternatives you've considered no alternatives.
Additional context A fix will also fix these: https://github.com/shinesolutions/puppet-aem-curator/issues/193 https://github.com/shinesolutions/puppet-aem-curator/issues/152