Skip to content

Comments

Implement tri-state disabled field for TLS configuration#1002

Merged
THardy98 merged 4 commits intomasterfrom
envconfig_tls_disabled_optional
Sep 8, 2025
Merged

Implement tri-state disabled field for TLS configuration#1002
THardy98 merged 4 commits intomasterfrom
envconfig_tls_disabled_optional

Conversation

@THardy98
Copy link
Contributor

@THardy98 THardy98 commented Sep 5, 2025

What was changed

Change TLS disabled field from bool to Option to support three states:

  • None: TLS behavior depends on other factors (API key, etc.)
  • Some(false): TLS explicitly enabled
  • Some(true): TLS explicitly disabled

This fixes TOML serialization asymmetry where "not set" vs "explicitly false" could not be distinguished, ensuring proper round-trip compatibility.

  1. How was this tested:
    Existing test suite passes, added test for tri-state disabled field.

  2. Any docs updates needed?
    No

Change TLS disabled field from bool to Option<bool> to support three states:
- None: TLS behavior depends on other factors (API key, etc.)
- Some(false): TLS explicitly enabled
- Some(true): TLS explicitly disabled

This fixes TOML serialization asymmetry where "not set" vs "explicitly false"
could not be distinguished, ensuring proper round-trip compatibility.
@THardy98 THardy98 marked this pull request as ready for review September 5, 2025 18:02
@THardy98 THardy98 requested a review from a team as a code owner September 5, 2025 18:02
@THardy98 THardy98 merged commit 882c866 into master Sep 8, 2025
18 checks passed
@THardy98 THardy98 deleted the envconfig_tls_disabled_optional branch September 8, 2025 16: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.

2 participants