Skip to content

Obsolete: Fastly runtime-env warning ran before logger initialization #359

Closed as not planned

Description

@aram356

Description

The missing-edgezero_runtime_env warning used to run before logger initialization and therefore disappear. That code path no longer exists: merged PR #381 removed the runtime-env store/loader architecture and moved physical store selection to deploy-time logical resource links.

Steps to reproduce

Historical reproduction: remove the runtime-env store and observe the warning emitted by the old loader before logger initialization.

Current inspection: current Fastly entry point initializes logging from baked configuration before registry dispatch. Runtime logical store metadata is documented at current logical-alias store metadata. The old missing-runtime-env-store reproduction cannot be performed on current main. No log-delivery test was executed.

Expected behavior

Current Fastly execution uses declared logical resource links and does not require an obsolete runtime-env store or emit its missing-store warning.

Impact

The original diagnostic-loss defect applied to removed architecture. Restoring the loader solely to repair its warning would reintroduce obsolete configuration state.

Proposed fix

Close as obsolete/not planned, superseded by PR #381. Any independently observed missing diagnostic in the current logical-binding path should be tracked against that path with fresh evidence.

Done when

  • Confirm the runtime-env loader/store and its warning are removed from current main.
  • Confirm current entry points configure logging before the relevant request dispatch.

Related

PR #351 introduced the exposed historical loader; PR #381 removed that architecture. current Fastly entry point.

Activity

  1. changed the title [-]Fastly: missing edgezero_runtime_env warning is emitted before logger init and never reaches Fastly logs[/-] [+]Obsolete: Fastly runtime-env warning ran before logger initialization[/+] on Nov 9, 2026
  2. added theissue type on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions