feat(api): Accept project slugs in product integration endpoints#117495
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
gricha
force-pushed
the
feat/project-id-or-slug-product-integrations
branch
from
0eea84c to
fa25a83
Compare
Allow code mappings, monitors, notification actions, and preprod snapshot lookups to resolve project inputs by ID or slug while keeping legacy projectSlug runtime support. Co-Authored-By: OpenCode <noreply@opencode.ai>
Keep the existing preprod latest-base projectSlug query metadata while documenting project as the canonical ID-or-slug query parameter. Co-Authored-By: OpenCode <noreply@opencode.ai>
Use the shared integer-or-string schema for the preprod latest-base project filter so generated clients can keep passing numeric project IDs. Co-Authored-By: OpenCode <noreply@opencode.ai>
gricha
force-pushed
the
feat/project-id-or-slug-product-integrations
branch
from
fa25a83 to
3b703a7
Compare
Use direct ID-or-slug branching for single-project lookups instead of the bulk project parser. This keeps sentinel rejection and permission behavior unchanged while making the control flow easier to read. Co-Authored-By: OpenCode <opencode@users.noreply.github.com>
JoshFerge
reviewed
Jun 15, 2026
JoshFerge
left a comment
JoshFerge
left a comment
Contributor
There was a problem hiding this comment.
can we not do more of this logic in the OrganizationEndpoint base?
Move single-project ID-or-slug parsing into OrganizationEndpoint so endpoints share projectSlug precedence, blank handling, and all-project sentinel rejection. Keep endpoint-specific project existence and queryset behavior at the call sites. Co-Authored-By: OpenCode <opencode@users.noreply.github.com>
JoshFerge
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code mapping bulk operations, monitor creation, notification actions, and preprod latest-base snapshot lookup now accept project IDs or slugs where those surfaces already accepted project identifiers. The changes keep existing permission checks, preserve existing
projectSlugruntime/schema compatibility, and document canonicalproject/projectsvalues as ID-or-slug without adding newprojectSlugOpenAPI parameters.This is the product integrations split from the project ID-or-slug migration stack and targets the resolver branch for independent review. Validated with focused product endpoint tests, targeted ruff,
git diff --check, andmake test-api-docs.