feat: support for two separate applications in hybrid mode

[jometzner]

PR Type

[ ] Bugfix
[ X ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:

What Is the Current Behavior?

Currently you can use the hybrid mode (see below) only with one application. This has drawbacks as PWA uses the application denoted by rest and the classic storefront uses -. Certain aspects of ICM are managed application specific (e.g. CMS data) making it mandatory to merge the two applications into one. To much effort.

What Is the New Behavior?

You can specify the used hybrid application identifier in your environment.ts or theme-specific environment.<theme>.ts with key hybridApplication.

export const environment: Environment = {
  ...ENVIRONMENT_DEFAULTS,

  icmChannel: 'inSPIRED-inTRONICS_Business-Site',
  icmApplication: 'rest',
  hybridApplication: '-',

Does this PR Introduce a Breaking Change?

[ ] Yes
[ X ] No

Other Information

Hybrid mode is where PWA and classic storefront are used side-by-side. See hybrid-approach.md

AB#80090

[github-actions]

Azure Demo Servers are available:

• Hybrid B2B