Date: 2026-05-11
Focus: Offline backup implementation for foremanctl (porting from foreman-maintain)
The current plan in foremanctl-backup-implementation-plan.md provides a solid foundation but has critical gaps around IOP (Insights Operator Platform) database handling. This evaluation identifies these gaps and proposes a corrected design aligned with the actual running services on this system.
This foremanctl deployment uses Podman Quadlets - a declarative system that converts container definitions into systemd services. All backend services (PostgreSQL, Redis, Pulp, Candlepin) and the main Foreman application run as containers managed by systemd with host networking mode.
Key Difference from Dev Setup:
bundle exec foreman startpodman exec
foremanctl deploys Foreman and Katello using Podman Quadlets - a declarative system that converts container definitions into systemd services. All backend services run as containers managed by systemd.
/home/vagrant/foreman/ (vagrant user)
Problem: Katello depends on 9 pre-packaged Pulp Ruby client gems that the Pulp team struggles to maintain and package. These gems must be kept in sync with Pulp versions, creating a packaging bottleneck.
Solution: Generate Ruby API clients from OpenAPI specs in development, commit generated code to repository, and package with Katello RPM. This eliminates dependency on Pulp team's gem packaging while catching all generation issues in Dev/QE before customer release.
I want a prompt to start a team of claude agents, one which works on Katello repository to convert Contentcredentials Details page to React with all the subtabs that exist in the engines/bastion_katello code for Content Credentials with routing via experimental labs under /labs/ route. I want another agent which writes the tests based on the conversion by conversion agent. I want another agent that creates airgun entities for the new components so they can be tested and then a robottelo agent that uses these new entities to come up with good tests for the new details page. Give me such a prompt which creates that team and opens a tmux split pane session.
| { | |
| "env": { | |
| "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" | |
| }, | |
| "preferences": { | |
| "tmuxSplitPanes": true | |
| }, | |
| "skipDangerousModePermissionPrompt": true | |
| } |
| rtl-code-reviewer │ | |
| │ /home/sajha/.claude/agents/rtl-code-reviewer.md │ | |
| │ │ | |
| │ Description (tells Claude when to use this agent): │ | |
| │ Use this agent to review React tests when prompted to review a RTL test |
| name | snapshottests-rtl-converter |
|---|---|
| description | Converts Enzyme snapshot tests to React Testing Library tests with realistic fixtures and API mocking |
| tools | Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell, ListMcpResourcesTool, ReadMcpResourceTool |
| model | sonnet |
| color | pink |
You are an experienced React Javascript engineer who is proficient in writing and understanding react tests
name: angular-to-react-migrator description: Use this agent when working on migrating AngularJS components from the engines/bastion_katello directory to React in the webpack directory of the katello/katello repository. Specifically invoke this agent when:\n\n\nContext: User is starting to migrate an AngularJS workflow to React.\nuser: "I need to migrate the content views workflow from AngularJS to React"\nassistant: "I'm going to use the Task tool to launch the angular-to-react-migrator agent to help with migrating the content views workflow from AngularJS to React."\n\nThe user is requesting a migration from AngularJS to React, which is exactly what this agent specializes in. Use the Agent tool to invoke the angular-to-react-migrator.\n\n\n\n\nContext: User has just written a new React component as part of a migration.\nuser: "I've created the new ContentViewsIndex component in webpack/components/ContentViews/"\nassistant: "Great! Let me use the angula