At the moment HPP does an excellent job in building and merging config files for a single role. From a CI/CD perspective, i'd like to be able to generate, in a single build/publish, all the configuration files which are role specific. Which means that, next to the merged parameters.xml and (optional) transformation file "web.helix.config" there will be a parameters..xml and web.helix..config
you'd be able to generate, in a single build, all binaries/assets that are needed for a role specific package, as the required role specific paramters.role.xml and web.helix.role.config would be available to create a role specific web.config and build a role specific web deploy package, without having to build the solution multiple times using different configurations -> this would save a lot of valuable build time
My proposol would be to, add the following functionality:
Parameters.xml:
Parameters..xml parameter files in the different solutions would be merged into parameters..xml
web.helix..config files in the different solutions would be merged into web.helix.role.config
The web.helix.role approach might conflict with this issue so it's something to look out for.
At the moment HPP does an excellent job in building and merging config files for a single role. From a CI/CD perspective, i'd like to be able to generate, in a single build/publish, all the configuration files which are role specific. Which means that, next to the merged parameters.xml and (optional) transformation file "web.helix.config" there will be a parameters..xml and web.helix..config
you'd be able to generate, in a single build, all binaries/assets that are needed for a role specific package, as the required role specific paramters.role.xml and web.helix.role.config would be available to create a role specific web.config and build a role specific web deploy package, without having to build the solution multiple times using different configurations -> this would save a lot of valuable build time
My proposol would be to, add the following functionality:
Parameters.xml: Parameters..xml parameter files in the different solutions would be merged into parameters..xml
web.helix..config files in the different solutions would be merged into web.helix.role.config
The web.helix.role approach might conflict with this issue so it's something to look out for.