-
Notifications
You must be signed in to change notification settings - Fork 127
Use deploy-satellite-iop workflow for module_satellite_iop fixture #19995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tpapaioa
wants to merge
1
commit into
SatelliteQE:master
Choose a base branch
from
tpapaioa:deploy_satellite_iop
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+25
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a88f483
to
8d37b92
Compare
8d37b92
to
ebfb0e3
Compare
|
PRT Result
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey there - I've reviewed your changes - here's some feedback:
- Wrap your teardown and Broker.checkin calls in a finalizer (or try/finally) so cleanup always runs even if the IoP assertion or a downstream error fails.
- Consider moving the IoP‐enabled assertion out of the fixture and into the tests themselves to keep fixtures focused on setup/teardown.
- Verify that any tests relying on the old module_unconfigured_satellite fixture are updated to use the new satellite_factory signature to prevent fixture resolution errors.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Wrap your teardown and Broker.checkin calls in a finalizer (or try/finally) so cleanup always runs even if the IoP assertion or a downstream error fails.
- Consider moving the IoP‐enabled assertion out of the fixture and into the tests themselves to keep fixtures focused on setup/teardown.
- Verify that any tests relying on the old module_unconfigured_satellite fixture are updated to use the new satellite_factory signature to prevent fixture resolution errors.
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
jameerpathan111
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
6.18.z
Introduced in or relating directly to Satellite 6.18
CherryPick
PR needs CherryPick to previous branches
PRT-Passed
Indicates that latest PRT run is passed for the PR
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Statement
The
module_satellite_iop
fixture should use the newdeploy-satellite-iop
AAP workflowSolution
Update the fixture to use the workflow defined in the
server.deploy_workflows.iop
setting.Related Issues