Skip to content

chore: Do not forbid extra fields in Pydantic models to fix incosistency between models and current SLE APIs - #221

Merged
spanglerco merged 1 commit into
1.6.xfrom
do-not-forbid-extra-fields
Jul 15, 2026
Merged

spanglerco merged 1 commit into
1.6.xfrom
do-not-forbid-extra-fields

Conversation

@AlexDanDuna

@AlexDanDuna AlexDanDuna commented Jul 15, 2026 •

Copy link
Copy Markdown
Contributor

What does this Pull Request accomplish?

Two tests for the File and Spec clients are failing, since api info now returns operations that are not properly modeled in their Operations:
Log of failed workflow step:
6_Run poetry run pytest --cloud-api-key --enterprise-uri https_test-api.lifecyclesolutions.ni.com --enterprise-api-key .txt

Skip forbidding extra fields in conftest.py to get the tests to run. Thanks to @spanglerco for suggesting the fix.

Why should this Pull Request be merged?

We're aiming to release a patch for SLS from this branch; enforcing that the models match the current SLE APIs, in this old library version, is out of scope.

What testing has been done?

Pipeline passes

@spanglerco
spanglerco merged commit 4b302c6 into 1.6.x Jul 15, 2026
8 checks passed
@spanglerco
spanglerco deleted the do-not-forbid-extra-fields branch July 15, 2026 19:20
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