Skip to content

fix: return an explicit error when application creation yields an empty response - #63

Open
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:fix/create-application-empty-response
Open

fix: return an explicit error when application creation yields an empty response#63
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:fix/create-application-empty-response

Conversation

@mjdavidson

Copy link
Copy Markdown

create_application returned None when the SDK accepted the call but responded with an empty body (no app and no error), so a rejected/normalized configuration looked like a silent no-op. Adds a guard that returns a clear error when no application and no error come back; valid input is unaffected.

Tests: tests/test_create_application.py.

…ty response

When the Okta SDK accepts a create-application call but responds with no body
(for example when a configuration value is silently rejected or normalized
away), it returns neither an application object nor an error. The handler only
checked for an error and returned the empty result as-is, so the tool surfaced
no content and no explanation, making a rejected configuration look like a
successful no-op.

Add a guard that returns a clear error when the SDK returns no application and
no error. Valid input is unaffected and still returns the created application.
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.

1 participant