Skip to content

Conversation

@nirarg
Copy link
Collaborator

@nirarg nirarg commented Aug 27, 2025

Summary by Sourcery

Update default container registry organization to redhat-user-workloads/assisted-migration-tenant and remove the obsolete build-push-images GitHub Actions workflow.

Enhancements:

  • Change default REGISTRY_ORG in the Makefile from kubev2v to redhat-user-workloads/assisted-migration-tenant

CI:

  • Delete the build-push-images.yml workflow from .github/workflows

Summary by CodeRabbit

  • Chores
    • Removed a legacy CI workflow that built and published container images.
    • Updated the default container image namespace used by the project to a new organization.
  • Documentation
    • Updated docs and examples to reference the new image namespace and fixed trailing newline formatting.
  • User Defaults
    • Updated default agent image used by CLI and tooling to the new namespace; no behavioral changes to interfaces.

@sourcery-ai
Copy link

sourcery-ai bot commented Aug 27, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR updates the image registry organization reference in the Makefile to point to the new ‘redhat-user-workloads/assisted-migration-tenant’ namespace and removes the obsolete GitHub Actions build-push-images workflow.

File-Level Changes

Change Details Files
Change image registry organization in Makefile
  • Replaced REGISTRY_ORG from ‘kubev2v’ to ‘redhat-user-workloads/assisted-migration-tenant’
Makefile
Remove outdated GitHub Actions workflow
  • Deleted the build-push-images.yml file
.github/workflows/build-push-images.yml

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

@coderabbitai
Copy link

coderabbitai bot commented Aug 27, 2025

Walkthrough

Deleted a GitHub Actions workflow that built and pushed container images and switched default image references and docs from quay.io/kubev2v to quay.io/redhat-user-workloads/assisted-migration-tenant. No public API or exported signatures were changed.

Changes

Cohort / File(s) Summary
CI workflow removal
.github/workflows/build-push-images.yml
Deleted workflow that built and pushed images to Quay (triggered on main and workflow_dispatch), including Quay login, tag logic, make build-containers and make push-containers steps.
Registry/config change — build & runtime
Makefile, data/ignition.template, internal/image/builder.go, internal/cli/generate.go
Replaced default image organization from kubev2v to redhat-user-workloads/assisted-migration-tenant for agent/api image references and defaults used by the image builder and CLI generate defaults; ignition template destination image updated accordingly.
Docs update
doc/cli.md, doc/deployment.md, doc/githubworkflows.md, doc/troubleshooting.md
Updated documentation and examples to use new quay.io paths under redhat-user-workloads/assisted-migration-tenant; minor EOF/newline formatting fixes.

Sequence Diagram(s)

(omitted — changes are configuration and delete-only, no new control flow to visualize)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • machacekondra
  • tupyy
  • ronenav
  • Jos-Jerus

Poem

I thump on logs where builders played,
The workflow's gone, the paths relayed.
New nests in redhat fields I spy,
I wiggle whiskers, give a sigh.
Hooray — a carrot for the sky 🥕

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@sourcery-ai sourcery-ai bot left a 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 and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@nirarg nirarg changed the title NO-JIRA | ci: remove "kubev2v" registry, use "redhat-user-workloads/assisted-migration-tenant" instead [WIP] NO-JIRA | ci: remove "kubev2v" registry, use "redhat-user-workloads/assisted-migration-tenant" instead Aug 27, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
Makefile (1)

5-5: GO_FILES glob is incorrect; rebuilds may miss source changes

-name ".go" matches only a file literally named .go. This likely prevents container rebuilds on source edits.

-GO_FILES := $(shell find ./ -name ".go" -not -path "./bin" -not -path "./packaging/*")
+GO_FILES := $(shell find ./ -name "*.go" -not -path "./bin/*" -not -path "./packaging/*")
🧹 Nitpick comments (2)
Makefile (2)

156-157: Avoid hard-coding registry in login

Use $(REGISTRY) instead of quay.io to keep REGISTRY overrideable.

-		$(PODMAN) login --authfile $(DOCKER_AUTH_FILE) -u=$(QUAY_USER) -p=$(QUAY_TOKEN) quay.io; \
+		$(PODMAN) login --authfile $(DOCKER_AUTH_FILE) -u=$(QUAY_USER) -p=$(QUAY_TOKEN) $(REGISTRY); \

13-14: Optional: deduplicate registry path construction

Minor readability improvement by introducing REGISTRY_PATH.

+REGISTRY_PATH := $(REGISTRY)/$(REGISTRY_ORG)
-MIGRATION_PLANNER_AGENT_IMAGE ?= $(REGISTRY)/$(REGISTRY_ORG)/migration-planner-agent
-MIGRATION_PLANNER_API_IMAGE ?= $(REGISTRY)/$(REGISTRY_ORG)/migration-planner-api
+MIGRATION_PLANNER_AGENT_IMAGE ?= $(REGISTRY_PATH)/migration-planner-agent
+MIGRATION_PLANNER_API_IMAGE ?= $(REGISTRY_PATH)/migration-planner-api
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between def2186 and 75e16e3.

📒 Files selected for processing (2)
  • .github/workflows/build-push-images.yml (0 hunks)
  • Makefile (1 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/build-push-images.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Red Hat Konflux / migration-planner-agent-on-pull-request
  • GitHub Check: Red Hat Konflux / migration-planner-api-on-pull-request
  • GitHub Check: unit-test
  • GitHub Check: test
  • GitHub Check: lint

VERBOSE ?= false
REGISTRY ?= quay.io
REGISTRY_ORG ?= kubev2v
REGISTRY_ORG ?= redhat-user-workloads/assisted-migration-tenant
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Registry org change: confirm repo and creds exist in new namespace

Switching to redhat-user-workloads/assisted-migration-tenant looks fine. Please verify:

  • The repositories for migration-planner-agent and migration-planner-api exist under this org and you have push rights.
  • Any docs/automation that referenced kubev2v are updated accordingly (since the build/push workflow was removed).

Run to spot leftovers:


🏁 Script executed:

#!/bin/bash
# Find old registry/org references and deleted workflow remnants
rg -nPI 'kubev2v|quay\.io/kubev2v' -g '!*vendor*'
rg -nPI '\.github/workflows/build-push-images\.yml|Build and push images'

Length of output: 26888


🏁 Script executed:

#!/bin/bash
# Locate file paths for hardcoded quay.io/kubev2v references
rg -nH 'defaultAgentImage' || true
rg -nH 'skopeo copy.*quay\.io/kubev2v' || true

Length of output: 634


Registry org change: update remaining quay.io/kubev2v references

We’ve confirmed that two hard-coded quay.io/kubev2v paths remain and must be updated to use the new $(REGISTRY_ORG) (i.e. redhat-user-workloads/assisted-migration-tenant):

  • internal/image/builder.go:
    • Line 35: defaultAgentImage = "quay.io/kubev2v/migration-planner-agent"
      → should be $(REGISTRY_ORG)/migration-planner-agent instead of the quay.io path.
  • data/ignition.template:
    • Lines 122 & 125: skopeo copy commands targeting
      containers-storage:quay.io/kubev2v/migration-planner-agent:latest (and the forklift-validation image)
      → these should reference $(REGISTRY_ORG)/migration-planner-agent:latest (and, if applicable, the new org for forklift-validation).

Next steps:

  • Update those constants/templates to use $(REGISTRY_ORG)
  • Ensure the migration-planner-agent and migration-planner-api repos exist under redhat-user-workloads/assisted-migration-tenant and that you have push rights.
  • Scan docs and automation for any other quay.io/kubev2v references and update accordingly.
🤖 Prompt for AI Agents
In Makefile line 10 and related files: internal/image/builder.go line 35 and
data/ignition.template lines 122 and 125, there are remaining hard-coded
quay.io/kubev2v paths that must be replaced with the new REGISTRY_ORG variable;
update internal/image/builder.go to construct defaultAgentImage as
"$(REGISTRY_ORG)/migration-planner-agent" (or use the existing Go build-time var
pattern), and update the skopeo copy lines in data/ignition.template to
reference "$(REGISTRY_ORG)/migration-planner-agent:latest" (and the equivalent
for forklift-validation) instead of containers-storage:quay.io/..., then verify
the migration-planner-agent and migration-planner-api repos exist under
redhat-user-workloads/assisted-migration-tenant and you have push rights, and
finally scan docs/automation for any other quay.io/kubev2v occurrences and
replace them with $(REGISTRY_ORG).

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
Makefile (1)

5-5: Bug: GO_FILES pattern matches only a file literally named “.go”.

This breaks change detection for container rebuild deps. Use *.go and fix path exclusions.

-GO_FILES := $(shell find ./ -name ".go" -not -path "./bin" -not -path "./packaging/*")
+GO_FILES := $(shell find . -type f -name "*.go" -not -path "./bin/*" -not -path "./packaging/*")
♻️ Duplicate comments (1)
Makefile (1)

10-10: Update remaining quay.io/kubev2v references across the repo.

Past scans showed hard-coded kubev2v paths (e.g., internal/image/builder.go defaultAgentImage, data/ignition.template skopeo lines). Update them to respect $(REGISTRY)/$(REGISTRY_ORG).

#!/bin/bash
rg -nPI 'quay\.io/kubev2v|[^A-Za-z]kubev2v[^A-Za-z]'
🧹 Nitpick comments (3)
Makefile (3)

153-158: Make registry login honor $(REGISTRY).

quay-login hardcodes quay.io; switch to $(REGISTRY) to keep targets portable.

-		$(PODMAN) login --authfile $(DOCKER_AUTH_FILE) -u=$(QUAY_USER) -p=$(QUAY_TOKEN) quay.io; \
+		$(PODMAN) login --authfile $(DOCKER_AUTH_FILE) -u=$(QUAY_USER) -p=$(QUAY_TOKEN) $(REGISTRY); \

13-14: DRY the base registry namespace.

Reduce duplication and simplify future changes by factoring a base variable.

+REGISTRY_NS ?= $(REGISTRY)/$(REGISTRY_ORG)
-MIGRATION_PLANNER_AGENT_IMAGE ?= $(REGISTRY)/$(REGISTRY_ORG)/migration-planner-agent
-MIGRATION_PLANNER_API_IMAGE ?= $(REGISTRY)/$(REGISTRY_ORG)/migration-planner-api
+MIGRATION_PLANNER_AGENT_IMAGE ?= $(REGISTRY_NS)/migration-planner-agent
+MIGRATION_PLANNER_API_IMAGE ?= $(REGISTRY_NS)/migration-planner-api

61-76: Deduplicate help output.

The help target prints duplicate entries (generate, tidy, lint, build, clean). Trim the second block.

 	@echo "    setup-opa-policies:     download OPA policies from Forklift project"
 	@echo "    clean-opa-policies:     clean OPA policies directory"
-	@echo "    generate:        regenerate all generated files"
-	@echo "    tidy:            tidy go mod"
-	@echo "    lint:            run golangci-lint"
-	@echo "    build:           run all builds"
-	@echo "    clean:           clean up all containers and volumes"
 	@echo "    migrate:         run database migrations"
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 75e16e3 and d1ab20b.

📒 Files selected for processing (2)
  • .github/workflows/build-push-images.yml (0 hunks)
  • Makefile (1 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/build-push-images.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Red Hat Konflux / migration-planner-api-on-pull-request
  • GitHub Check: Red Hat Konflux / migration-planner-agent-on-pull-request
  • GitHub Check: unit-test
  • GitHub Check: test
  • GitHub Check: lint
🔇 Additional comments (1)
Makefile (1)

10-14: Verify Quay repository path composition

Please confirm that using a two-segment namespace in REGISTRY_ORG (i.e. redhat-user-workloads/assisted-migration-tenant) is valid in Quay—this produces image names like

quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent

Quay’s registry v2 API allows slash-separated repository names, but some organizations treat only the first segment as the namespace. Make sure that:

  • The full path (redhat-user-workloads/assisted-migration-tenant) is indeed registered as a single “repository” in Quay, not as two nested namespaces.
  • You have push (write) permissions for both migration-planner-agent and migration-planner-api under that path.

You can verify existence (and infer permissions) by checking the manifest endpoint—for example:

curl -I https://quay.io/v2/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent/manifests/latest
  • A 401 Unauthorized response indicates the repo exists but is private (you’ll need credentials to push).
  • A 404 Not Found means the path doesn’t exist as given and needs correction.

If this three-segment path isn’t valid, adjust REGISTRY_ORG to the correct namespace (e.g. redhat-user-workloads) or split out assisted-migration-tenant appropriately.

…ssisted-migration-tenant" instead

Signed-off-by: Nir Argaman <[email protected]>
@openshift-ci
Copy link

openshift-ci bot commented Sep 1, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nirarg

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
internal/image/builder.go (1)

445-464: Hardcoded persistence disk path/name — overrides configured value.

writePersistenceDisk ignores b.PersistentDiskImage and always packs data/persistence-disk.vmdk with a fixed name. This breaks overrides set via WithPersistentDiskImage and mismatches diskSize(). Use the configured path and a header name derived from it.

@@
-import (
+import (
   "archive/tar"
   "bytes"
   "context"
   "fmt"
   "io"
+  "path/filepath"
   "os"
   "text/template"
   "time"
 )
@@
 func (b *ImageBuilder) writePersistenceDisk(tw *tar.Writer) error {
-  diskContent, err := os.ReadFile("data/persistence-disk.vmdk")
+  diskContent, err := os.ReadFile(b.PersistentDiskImage)
   if err != nil {
     return err
   }
 
   header := &tar.Header{
-    Name:    "persistence-disk.vmdk",
+    Name:    filepath.Base(b.PersistentDiskImage),
     Size:    int64(len(diskContent)),
     Mode:    0600,
     ModTime: time.Now(),
   }
 
   if err := tw.WriteHeader(header); err != nil {
     return err
   }
-  if _, err := tw.Write([]byte(diskContent)); err != nil {
+  if _, err := tw.Write(diskContent); err != nil {
     return err
   }
 
   return nil
 }
🧹 Nitpick comments (3)
internal/image/builder.go (2)

35-35: Registry org switch looks good; consider tagging for consistency.

Elsewhere defaults use :latest. Consider aligning here to avoid surprises when comparing logs/docs.

- defaultAgentImage            = "quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent"
+ defaultAgentImage            = "quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent:latest"

322-327: Typo in error message.

"comute" → "compute".

-  return -1, fmt.Errorf("failed to comute persistent disk size: %s", err)
+  return -1, fmt.Errorf("failed to compute persistent disk size: %s", err)
doc/githubworkflows.md (1)

40-45: Fix list formatting for “Old/New Destination” and tighten wording.

Current Markdown renders unevenly (flagged by grammar tools). Use a single bullet with an arrow or a nested list.

Apply:

-- **Old Destination**: `quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent`  
-  **New Destination**: `quay.io/<YOUR-QUAY-USERNAME>/migration-planner-agent`
-
-- **Old Destination**: `quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api`  
-  **New Destination**: `quay.io/<YOUR-QUAY-USERNAME>/migration-planner-api`
+• `quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent` → `quay.io/<YOUR-QUAY-USERNAME>/migration-planner-agent`
+• `quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api` → `quay.io/<YOUR-QUAY-USERNAME>/migration-planner-api`
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d1ab20b and e3a04c7.

📒 Files selected for processing (9)
  • .github/workflows/build-push-images.yml (0 hunks)
  • Makefile (1 hunks)
  • data/ignition.template (1 hunks)
  • doc/cli.md (2 hunks)
  • doc/deployment.md (2 hunks)
  • doc/githubworkflows.md (3 hunks)
  • doc/troubleshooting.md (1 hunks)
  • internal/cli/generate.go (2 hunks)
  • internal/image/builder.go (1 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/build-push-images.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • Makefile
🧰 Additional context used
🪛 LanguageTool
doc/githubworkflows.md

[grammar] ~40-~40: There might be a mistake here.
Context: ... be as follows: - Old Destination: quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent New Destination: `quay.io/<YOUR-QUAY-U...

(QB_NEW_EN)


[grammar] ~43-~43: There might be a mistake here.
Context: ...-planner-agent - **Old Destination**:quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api **New Destination**:quay.io/<YOUR-QUAY-U...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Red Hat Konflux / migration-planner-api-on-pull-request
  • GitHub Check: Red Hat Konflux / migration-planner-agent-on-pull-request
  • GitHub Check: unit-test
  • GitHub Check: lint
  • GitHub Check: check-generate
  • GitHub Check: test
🔇 Additional comments (9)
doc/cli.md (2)

168-168: EOF newline fix — LGTM.


82-82: Default image updated; no quay.io/kubev2v references remain — verified no occurrences of quay.io/kubev2v/migration-planner-agent.

data/ignition.template (1)

121-123: Skopeo destination switched to new org — LGTM.

forklift-validation remains under kubev2v as expected.

doc/troubleshooting.md (1)

48-48: Sample output updated to new org — LGTM.

internal/cli/generate.go (2)

31-32: Default AgentImageURL updated — LGTM.

In sync with docs and template.


104-104: Flag default updated — LGTM.

Help text and default are consistent.

doc/deployment.md (2)

5-5: Update CI/publishing statement (workflow was removed in this PR).

This line claims images are built and pushed after each PR merge, but .github/workflows/build-push-images.yml was deleted. Either remove the claim or point to the current publishing process.

Apply:

-By default, images are deployed from the `quay.io/redhat-user-workloads/assisted-migration-tenant` namespace. New images are built and pushed to Quay after each PR is merged into this repository.
+By default, images are deployed from the `quay.io/redhat-user-workloads/assisted-migration-tenant` namespace.

27-31: Deployment doc defaults are correct; add clarification for tag usage.

The defaults in doc/deployment.md match the Makefile and code (MIGRATION_PLANNER_API_IMAGE/MIGRATION_PLANNER_AGENT_IMAGE default to quay.io/redhat-user-workloads/assisted-migration-tenant/* and MIGRATION_PLANNER_IMAGE_TAG defaults to latest). Add a one-liner below the snippet noting that MIGRATION_PLANNER_IMAGE_TAG applies to both API and agent images, and the UI image uses MIGRATION_PLANNER_UI_IMAGE_TAG.

doc/githubworkflows.md (1)

231-231: EOF rule change OK.

Separator change to --- is harmless; no action needed.

Comment on lines +65 to +66
`MIGRATION_PLANNER_AGENT_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent`
`MIGRATION_PLANNER_API_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Section likely stale: workflow was removed in this PR.

This whole “build-push-images.yml” section documents a workflow that no longer exists. Either mark it as deprecated with the removal date (Aug 27, 2025) and point to the new process, or remove the section.

If keeping the section for historical context, prepend a banner:

+# Note: The `build-push-images.yml` workflow was removed on 2025-08-27.
+# The instructions below are deprecated; see current release/publish docs or .github/workflows.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
`MIGRATION_PLANNER_AGENT_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent`
`MIGRATION_PLANNER_API_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api`
# Note: The `build-push-images.yml` workflow was removed on 2025-08-27.
# The instructions below are deprecated; see current release/publish docs or .github/workflows.
`MIGRATION_PLANNER_AGENT_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-agent`
`MIGRATION_PLANNER_API_IMAGE ?= quay.io/redhat-user-workloads/assisted-migration-tenant/migration-planner-api`
🤖 Prompt for AI Agents
In doc/githubworkflows.md around lines 65-66, the "build-push-images.yml"
workflow section is stale because the workflow was removed in this PR; either
remove the entire section referencing MIGRATION_PLANNER_AGENT_IMAGE and
MIGRATION_PLANNER_API_IMAGE, or mark it explicitly as deprecated by prepending a
short banner that states "Deprecated (removed Aug 27, 2025)" and add one
sentence pointing readers to the new build/push process (include the new
workflow file or docs link and any changed variables), and update or remove the
two image variable lines accordingly so the doc no longer advertises an obsolete
workflow.

@openshift-merge-robot
Copy link
Collaborator

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@machacekondra
Copy link
Contributor

/retest

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants