Org Web Adapter

Editing hungryroot/jira/be_7540_allow_staff_to_fetch_inactive_cookbooks_and_cookbookcollections_is_active_false.org

:PROPERTIES:
:ID:       7ca261bb-e303-4301-a080-bde671eaa8dc
:END:
#+title: BE-7540 Allow staff to fetch inactive Cookbooks and CookbookCollections (is_active = False)

- source :: https://hungryroot.atlassian.net/browse/BE-7540
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]]
- epic   :: [[id:2f37c7bc-6cb2-47ae-a513-f634e5c4cfbb][EP-627 Exp 232: Cookbook MVP]]
- sprint :: [[id:c4663d81-db80-4eb0-a898-9f2c4aea9023][HR BE Sprint 107]]
- status :: [[id:87ee4162-0c60-41e4-8863-89e3ca8bf2f5][Status - Code Review]]
- priority :: [[id:87c238a1-1c0d-4ee9-b8a5-6876cabb93b4][Priority - High]]
- points :: 1

* Description
Staff currently can only fetch Cookbook and CookbookCollection instances where
is_active = True. We need to extend the API/data-access layer so staff can also
query and retrieve inactive resources when explicitly requested.

** Background / Context

Staff workflows sometimes require reviewing or restoring previously deactivated
cookbooks and collections.

Today, these inactive records are effectively hidden from normal staff queries.

We want to maintain the default behavior (only active records) while adding an
explicit way for staff to include inactive ones.

** Requirements / Acceptance Criteria

Staff-facing API supports fetching:

Cookbook instances with is_active = False

CookbookCollection instances with is_active = False

Default behavior remains unchanged:

If no explicit flag is provided, only is_active = True records are returned.

Provide a clear, documented mechanism to include inactive items, for example:

A query parameter or filter flag (e.g. include_inactive=true or status=inactive)

Or an equivalent filter option at the data-access layer used by staff endpoints.

The mechanism:

Is available for both Cookbook and CookbookCollection queries.

Is only exposed on staff/internal endpoints, not public/consumer-facing ones
(confirm scope with PM if needed).

Add/update tests to cover:

Fetching only active items (current behavior)

Fetching inactive items only

Fetching both active and inactive when explicitly requested

Update relevant API or internal documentation to describe:

New query parameters / filter options

Any permission/scope limitations

** Technical Notes / Implementation Ideas

Introduce optional filter(s) on the repository/ORM layer for:

is_active in [True] (current default)

is_active in [False]

is_active in [True, False] when including inactive

Ensure any existing callers that assume “active only” continue to behave as-is
(no breaking changes).

Confirm any authorization/role constraints so only appropriate staff roles can
access inactive items.