Skip to content

Add live upgrade regression coverage for legacy Porter parameter overrides #5128

Open

Description

@JayDoubleu

Fresh deployments and SQL SKU changes do not prove that resources with legacy Porter parameter overrides can upgrade to the current installation format.

Current position

Item Status and evidence
Implementation No implementation PR yet.
Position Deferred coverage gap. No live upgrade-regression implementation or result is available.
Existing evidence #5139 covers a same-version SQL configuration change, not a prior-release migration.

Scope

  • Create a disposable prior-release resource that contains legacy overrides and record source/target versions.
  • Verify the documented upgrade-required response before affected custom actions or uninstall.
  • Upgrade through the supported template-version procedure, then verify custom actions, child resources and uninstall.

Remaining work

  • Implement a focused prior-release upgrade case, including the firewall parameter-file path where applicable.
  • Run it after ordinary bundle and backup validation, with bounded recovery and no secret logging.
  • Record retained resources, failure recovery and terminal cleanup.

Related earlier work: #2727, #4904. Run legacy Airlock migration #5129 afterwards.

Related work

Parent: #5124.

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

    bundlesCreating and deploying bundles/templatese2e-testsE2E testsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions