Skip to content

Keep user preferences out of config API subscriptions - #8

Merged
andre487 merged 1 commit into
mainfrom
fix/api-preserve-user-settings
Oct 12, 2026
Merged

andre487 merged 1 commit into
mainfrom
fix/api-preserve-user-settings

Conversation

@andre487

Copy link
Copy Markdown
Owner

Subscription responses previously included routeAllApps=true and other application defaults, which could overwrite locally configured split tunneling and preferences when imported or refreshed.

Limit API responses to profiles, connection parameters, credential inclusion flags and subscription endpoints/bootstrap settings. Omit root/profile routing, DNS, SSH tuning, failover, active/always-on selection, diagnostic limits and browser preferences, including explicit inventory overrides. Preserve explicit TLS/JA3 and technical browser fields (knockHost, authMode, masqueTemplate). A null subscription override no longer removes subscription endpoints. File exports retain their existing behavior.

Validation: 86 tests passed (test_config_api.py and test_inventory.py), Ruff and git diff --check passed. Already deployed to config_ru and config_kz with no Ansible failures; authenticated HTTPS responses checked on both hosts for generic, Android, Firefox and Chromium clients.

Client-side preservation of omitted settings still needs verification in the application.

@andre487
andre487 merged commit efe6059 into main Oct 12, 2026
10 checks passed
@andre487
andre487 deleted the fix/api-preserve-user-settings branch October 12, 2026 09:51
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