Skip to content

Add to_snap_version for upgrade-scenario tests#21705

Draft
tpapaioa wants to merge 1 commit into
SatelliteQE:masterfrom
tpapaioa:add_upgrade_to_snap_version
Draft

Add to_snap_version for upgrade-scenario tests#21705
tpapaioa wants to merge 1 commit into
SatelliteQE:masterfrom
tpapaioa:add_upgrade_to_snap_version

Conversation

@tpapaioa
Copy link
Copy Markdown
Contributor

@tpapaioa tpapaioa commented May 29, 2026

Problem Statement

Solution

Related Issues

SAT-40414

Summary by Sourcery

New Features:

  • Support configuring a target snapshot version for Satellite upgrade scenario tests via the upgrade settings.

@tpapaioa tpapaioa self-assigned this May 29, 2026
@tpapaioa tpapaioa added CherryPick PR needs CherryPick to previous branches Stream Introduced in or relating directly to Satellite Stream/Master 6.16.z 6.17.z 6.18.z Introduced in or relating directly to Satellite 6.18 6.19.z labels May 29, 2026
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 29, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds support for a separate snapshot version parameter in upgrade-scenario tests by wiring to_snap_version from the upgrade configuration into the upgrade job execution.

File-Level Changes

Change Details Files
Pass configured snapshot version into the satellite upgrade job for new-upgrades tests.
  • Extend the upgrade job invocation to include a new snap_version argument sourced from settings.upgrade.to_snap_version.
  • Ensure the snapshot version is part of the parameters passed to the upgrade action alongside existing upgrade settings.
tests/new_upgrades/conftest.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

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

Labels

6.16.z 6.17.z 6.18.z Introduced in or relating directly to Satellite 6.18 6.19.z CherryPick PR needs CherryPick to previous branches Stream Introduced in or relating directly to Satellite Stream/Master

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant