Broken 'Show configuration' state after viewing YAML

[momesgin]

Setup

• Rancher version: 2.14 and later
• Rancher UI Extensions:
• Browser type & version:

Describe the bug
When navigating to the YAML view of a resource via the action menu, clicking the "Show configuration" option fails to load the configuration form. Instead, an empty section is displayed.

To Reproduce

1. Navigate to a resource with a "View YAML" option in its action menu (e.g., Explorer > Workloads > Jobs > helm-install-traefik).
2. Open the action menu for the resource.
3. Select the "View YAML" option.
4. On the resulting detail page, click on the "Show configuration" option.

Result
The configuration form does not load; an empty section is displayed instead.

Expected Result

• After navigating to a resource via "View YAML" and then clicking "Show configuration", the configuration form renders correctly (matching the behaviour when navigating directly by clicking the resource name).
• No regression: navigating directly to a resource still loads the configuration form correctly.

Screenshots

dsadsdpskadsapok.mov

Additional context

• No console errors.
• If I navigate to the resource normally by clicking its name, the configuration form loads fine. The bug only occurs when transitioning from the "View YAML" action.

[github-actions]

🎯 Agentic Issue Triage

Summary: When a user navigates to a resource's detail page via the "View YAML" action menu option (which appends ?mode=_view&as=yaml to the URL), clicking "Show configuration" on that page results in an empty section rather than loading the configuration form. Navigating directly to the resource (without the YAML action) works correctly.

📋 Issue Analysis

Type: Bug — UI state regression triggered by a specific navigation path.

Affected Flow:

1. User uses action menu → "View YAML" → this calls goToViewYaml() in resource-class.js, pushing a route with ?mode=_view&as=yaml.
2. On the resulting detail page, the user clicks "Show configuration."
3. resource.showConfiguration() is invoked (via the show-configuration event chain → composables.ts in shell/components/Resource/Detail/).
4. showConfiguration() opens a ResourceDetailDrawer (SlideInPanel) with the config tab component loaded via store.getters['type-map/importEdit'](resource.type).
5. The drawer renders an empty config section instead of the form.

Key difference from the working path: When arriving normally (no ?as=yaml), the resource is fully hydrated and its component state is standard. When arriving via YAML action, TitleBar's currentView ref is initialized to yaml (line 59 in TitleBar/index.vue), and a watcher pushes a route with ?as=yaml whenever currentView changes. This route update could interfere with the drawer's rendering lifecycle (e.g., causing it to close prematurely due to closeOnRouteChange: ['name', 'params', 'query'] in showConfiguration()).

Root Cause Hypothesis: In resource-class.js line 927, closeOnRouteChange: ['name', 'params', 'query'] — "query" is included. When the TitleBar's currentView watcher fires (because the route already has ?as=yaml and the ref is initialized to yaml), it may push a route change that triggers the drawer to close before the configuration form is rendered. Alternatively, the as=yaml query param may prevent the config component from mounting correctly inside the drawer.

🔍 Relevant Code Locations

File	What to look at
shell/plugins/dashboard-store/resource-class.js ~L914	showConfiguration() — opens the drawer with closeOnRouteChange: ['name', 'params', 'query']
shell/plugins/dashboard-store/resource-class.js ~L1538	goToViewYaml() — pushes ?mode=_view&as=yaml
shell/components/Resource/Detail/TitleBar/index.vue L59	currentView initialized from query.as; watcher on L61 pushes route on change
shell/components/Drawer/ResourceDetailDrawer/composables.ts L15	useDefaultConfigTabProps() — gates Config tab on hasCustomEdit and hasCustomDetail
shell/components/Drawer/ResourceDetailDrawer/ConfigTab.vue	Renders the config form component
shell/components/SlideInPanelManager.vue	Manages the slide-in panel open/close lifecycle

🐛 Debugging Strategies

1. Check for premature drawer close: Add a console.log in SlideInPanelManager where it responds to route changes. Check if the drawer is opened and immediately closed when ?as=yaml is in the URL.

2. Check closeOnRouteChange: In showConfiguration(), try changing closeOnRouteChange to ['name', 'params'] (removing 'query') temporarily. If the config form loads, the bug is that the watcher in TitleBar triggers a query update that closes the drawer.

3. Check useDefaultConfigTabProps: Verify the resource type (helm-install-traefik Job) has both hasCustomEdit and hasCustomDetail returning true — if the config tab props return undefined, the tab won't render.

4. Check TitleBar watcher: The watcher fires when currentView value changes. Since the ref is initialized from query.as (which is yaml), it shouldn't fire on init. But confirm there's no reactive side-effect that triggers the watcher immediately after mount.

5. Add a breakpoint in showConfiguration() in resource-class.js and step through the slide panel opening; verify the component props are populated.

🔁 Reproduction Steps (Confirmed)

1. Start Rancher 2.14+
2. Navigate to Explorer → Workloads → Jobs
3. Find helm-install-traefik (or any Job with an action menu)
4. Open the ⋮ action menu → select "View YAML"
5. On the detail page (URL now has ?mode=_view&as=yaml), click "Show configuration"
6. ✅ Observe: empty section instead of the configuration form

Comparison (working):

• Click the Job's name to navigate normally (no ?as=yaml)
• Click "Show configuration"
• ✅ Configuration form loads correctly

✅ Suggested Fix Checklist

• Investigate whether closeOnRouteChange in showConfiguration() is reacting to the watcher push in TitleBar
• Check if removing 'query' from closeOnRouteChange (or filtering out as/mode query changes specifically) resolves the issue
• Alternatively, check if TitleBar's watcher should be suppressed when the drawer is open
• Confirm the fix works for multiple resource types (Jobs, Deployments, etc.)
• Add a unit/E2E test covering the "navigate via View YAML → click Show configuration" flow
• Verify no regression in the normal "Show configuration" flow

Generated by Agentic Triage for issue #17654 · ● 881.4K · ◷

[github-actions]

🤖 Issue grooming questions

Thanks for the clear bug report with steps and a video! One primary criterion is still needed before this can be triaged.

Missing: Acceptance Criteria

Please add 1–3 concrete, testable criteria defining what "fixed" looks like. For example:

• After navigating to a resource via "View YAML" and then clicking "Show configuration", the configuration form renders correctly (matching the behaviour when navigating directly by clicking the resource name).
• No regression: navigating directly to a resource still loads the configuration form correctly.

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ● 499K · ◷