Skip to content

enterprise.md

Latest commit

 

History

History
34 lines (27 loc) · 1.75 KB

enterprise.md

File metadata and controls

34 lines (27 loc) · 1.75 KB
Raw

Enterprise deployment

This plugin is driven entirely by one file — copilot-otel-logging.toml — so deploying it at scale is mostly a matter of distributing that config (and, optionally, any secrets it references) to managed devices.

Managing the TOML file at scale

Ship copilot-otel-logging.toml to each user's config location (~/.copilot/copilot-otel-logging.toml, or a path you set in $COPILOT_OTEL_CONFIG / $COPILOT_HOME) using your existing device-management tooling:

  • Microsoft Intune — deploy the file with a platform script / custom configuration profile (Windows) or a shell-script policy (macOS), or package it as a Win32/.pkg app. Reference secrets (e.g. Authorization = "Bearer ${OTEL_TOKEN}") via a managed environment variable rather than baking tokens into the file.
  • Jamf / Munki / other MDM (macOS) — distribute the file via a configuration profile or package payload.
  • Group Policy, SCCM/MECM, Ansible, Chef, Puppet, or a dotfiles repo — copy the file into place and keep it in sync from your source of truth.

Because the dispatcher expands ${ENV} / $ENV in [otel.headers] at runtime, you can keep the TOML identical across the fleet and inject per-user or per-environment secrets through managed environment variables.

Enterprise-managed plugins

For centrally governing which plugins run in your organization — including signing, distribution, and allow-listing — follow GitHub's enterprise plugin standards. Package this plugin and its config to meet those standards before rolling it out across a managed Copilot deployment.