New Relic APM agent configuration rollback after schema change

Goal

Determine whether a New Relic APM agent configuration rolls back cleanly with an application deployment after a database or application schema change, when configuration is split between newrelic.yml and environment variables.

Constraints and uncertainty

Environment variables generally override YAML values for supported keys, but not every newrelic.yml setting has an environment-variable equivalent, and support varies by agent language and version. Stale environment variables in container images or orchestration manifests can survive a rollback and re-enable a previous configuration unintentionally. New Relic agents do not manage database schema rollback, so agent configuration rollback must be considered separately from schema changes.

Assuming a standard containerized deployment with both newrelic.yml and environment-variable configuration, which agent keys remain YAML-only, and do persisted environment variables override restored YAML values after rollback?

• Which configuration keys in the target New Relic APM agent version support environment-variable overrides, and which are YAML-only?
• Do environment variables embedded in a container image or Kubernetes manifest persist across a deployment rollback and override restored newrelic.yml settings?
• Should agent configuration rollback be scripted separately from application or database schema rollback?