Skip to content

BRANDCON: pass host env into brand concierge bootstrap() - #6659

Open
loganzartman wants to merge 1 commit into
mainfrom
lzartman/brandcon-newrelic-env
Open

BRANDCON: pass host env into brand concierge bootstrap()#6659
loganzartman wants to merge 1 commit into
mainfrom
lzartman/brandcon-newrelic-env

Conversation

@loganzartman

@loganzartman loganzartman commented Sep 4, 2026

Copy link
Copy Markdown

What

Forward the milo env name (stage | prod | local) from getConfig() into the Brand Concierge web client's bootstrap() call.

window.adobe.concierge.bootstrap({
  instanceName: 'alloy',
  stylingConfigurations: getUpdatedChatUIConfig(),
  selector: `#${mountId}`,
  env: env?.name,          // <-- added
  onBeforeEventSend,
  onEvent: (event) => { bcAnalytics(event); },
});

Why

The web client is adding its own NewRelic browser monitoring and needs to route telemetry to the correct browser-app entity (stage vs prod). Rather than sniff the hostname inside the embeddable client, milo already has the authoritative env signal — so we pass it through.

Merge-order independence

The web client treats env as optional and defaults to stage when absent, so this PR and the web-client PR can merge in either order without breaking anything.

Scope / notes

  • Single call site (bcBootstrap); the global-nav variant reuses it.
  • Additive field only — existing bcBootstrap unit test asserts individual fields and continues to pass.
  • A parallel copy exists at libs/c2/blocks/brand-concierge/bc-bootstrap.js; left untouched here since env is optional (those surfaces safely default to stage). Can follow up if desired.

🤖 Generated with Claude Code

Forward the milo env name (stage|prod|local) to the brand concierge
web client's bootstrap() call so the client can route its own NewRelic
telemetry to the matching browser app entity.

The web client treats env as optional (defaults to stage), so this and
the web-client change can merge in either order.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aem-code-sync

aem-code-sync Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

SNOW Change Request Transaction ID: 0000019c1ef37582-210fcd23

@narcis-radu narcis-radu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @loganzartman - I am requesting changes because I noticed some missing / incorrect elements:

  • PR is against main, we're bypassing the normal flow. Unless this is tied to an exceptional release request, the code should go to stage first.
  • PR does not provide any QA / test pages
  • PR does not handle C2 blocks. I see a mention about the C2 block being left untouched, but I really want to understand whether the change is needed or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants