Skip to content

Default agentic_app_blueprint_id to app client id in get_agentic_identity#494

Merged
heyitsaamir merged 1 commit into
feature_agent365_supportfrom
heyitsaamir-default-blueprint-id-to-app-id
Jul 7, 2026
Merged

Default agentic_app_blueprint_id to app client id in get_agentic_identity#494
heyitsaamir merged 1 commit into
feature_agent365_supportfrom
heyitsaamir-default-blueprint-id-to-app-id

Conversation

@heyitsaamir

Copy link
Copy Markdown
Collaborator

Summary

App.get_agentic_identity(...) previously passed agentic_app_blueprint_id straight through, which meant it could be None if the caller didn't provide it. This change makes it default to the app's own client/app id (self.id) when omitted, mirroring the existing resolved_tenant_id style for readability.

Behavior change

  • Before: agentic_app_blueprint_id=None when the caller didn't pass one.
  • After: agentic_app_blueprint_id falls back to self.id (the app's client_id) when omitted. An explicitly provided value is still preserved.

Tests

Added two unit tests in packages/apps/tests/test_app.py:

  • explicitly provided agentic_app_blueprint_id is preserved
  • omitting it falls back to the app's client_id

All checks green: ruff format, ruff check, pyright (0 errors), and pytest packages (692 passed).

Note

This stacks on the Agent 365 feature branch (#464) and targets feature_agent365_support as its base — not main.

…tity

When agentic_app_blueprint_id is omitted in App.get_agentic_identity, it now
defaults to the app's own client/app id (self.id) instead of passing None
through to AgenticIdentity. Mirrors the existing tenant-resolution style.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@heyitsaamir heyitsaamir requested review from corinagum and lilyydu and removed request for lilyydu July 2, 2026 21:54
@heyitsaamir heyitsaamir merged commit 3b441b8 into feature_agent365_support Jul 7, 2026
5 checks passed
@heyitsaamir heyitsaamir deleted the heyitsaamir-default-blueprint-id-to-app-id branch July 7, 2026 20:28
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.

3 participants