Skip to content

chore(sdk): upgrade firewall manager sdk - #39

Merged
huides00 merged 4 commits into
mainfrom
fix/upgrade-sccfm-sdk-1.22.1573-pr
Sep 18, 2026
Merged

huides00 merged 4 commits into
mainfrom
fix/upgrade-sccfm-sdk-1.22.1573-pr

Conversation

@huides00

Copy link
Copy Markdown
Collaborator

Description

Update the SCCFM SDK to support UNKNOWN compliance and license statuses returned by the API for devices whose licensing state cannot be determined. The lockfile and regression coverage are updated accordingly. The full offline test suite passes with 1660 tests.

Upgrade scc-firewall-manager-sdk to 1.22.1573 so inventory responses with UNKNOWN compliance and license statuses deserialize correctly. Refresh the lockfile and add regression coverage for the new contract.

def test_generated_sdk_is_pinned_to_the_verified_compatible_version() -> None:
assert "scc-firewall-manager-sdk==1.17.27" in _project_config()["dependencies"]
assert "scc-firewall-manager-sdk==1.22.1573" in _project_config()["dependencies"]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if there will be another change of this version, wouldn't it break the test again? Can we take it from somewhere in that case?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. We should keep the SDK pinned to an exact version rather than always pulling the latest, because generated SDK releases can introduce breaking API changes and we want to catch that.

Use DeviceDeploymentsApi for multi-device FTD deployments introduced by SDK 1.22.1573 while retaining InventoryApi for single-device operations. Update regression tests and derive the SDK pin from pyproject so future upgrades do not duplicate the version string.
Add the 0.42.1 Ansible release entry required by release preparation so the next patch release preserves the existing changelog history.
Read the SDK requirement from the built package metadata instead of retaining the old version literal. Require one exact pin and verify the installed SDK matches it so future deliberate SDK bumps are validated automatically.
@github-actions

Copy link
Copy Markdown

Consistency Check

No consistency issues found.

Checker output
✓ No issues found across 4 file(s).

@huides00
huides00 merged commit 10e4c4b into main Sep 18, 2026
5 checks passed
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