Skip to content

Conversation

@Shahzaibyy
Copy link
Contributor

fix: fix 404 when editing inactive resources #1549

Add include_inactive query parameter support to allow editing
inactive resources in admin UI with ?include_inactive=true

Include inactive resources when fetching resource details for editing.
This fixes the 404 error that occurred when clicking Edit on an inactive
resource in the admin UI.

Closes IBM#1545

Signed-off-by: Mihai Criveti <crivetimihai@gmail.com>
@crivetimihai crivetimihai force-pushed the fix/1545-inactive-resource-404 branch from 862a5a5 to 4c6467e Compare December 13, 2025 01:27
Copy link
Member

@crivetimihai crivetimihai left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! I've rebased and simplified this PR.

Changes made:

  • Removed unrelated commits (uv installation support, OAuth logging/depth handling)
  • Fixed a bug where resource_id type was changed from str to int (would break UUID lookups)

The fix: The admin endpoint for fetching resource details now passes include_inactive=True to the service, allowing inactive resources to be edited. This is cleaner than adding a query parameter since admins should always be able to edit any resource regardless of active/inactive status.

@crivetimihai crivetimihai merged commit 8ca34d5 into IBM:main Dec 13, 2025
46 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants