add tests for configid and no configid

Author: mtoffl01

boolean-conversion-proposal.md

@@ -0,0 +1,139 @@
+# Proposal: Standardize Configuration Type Conversion Behavior
+
+## Summary
+
+We propose standardizing configuration type conversion behavior across all data types in the next major release, specifically changing how invalid boolean values are handled to match the behavior of other numeric types.
+
+## Current Problem
+
+### Inconsistent Behavior Between Data Types
+
+Currently, our configuration system exhibits inconsistent behavior when handling invalid values:
+
+**Numeric Types (Integer, Float, Double, Long):**
+```java
+// Environment: DD_SOME_INT=invalid_number
+int value = configProvider.getInteger("some.int", 42);
+// Result: 42 (default value) ✅
+```
+
+**Boolean Type:**
+```java
+// Environment: DD_SOME_BOOL=invalid_boolean  
+boolean value = configProvider.getBoolean("some.bool", true);
+// Result: false (hardcoded fallback) ❌
+```
+
+### Why This Is Problematic
+
+1. **Unexpected Behavior**: Users expect invalid values to fall back to their explicitly provided defaults
+2. **Silent Failures**: Invalid boolean configurations silently become `false`, making debugging difficult
+3. **API Inconsistency**: Different data types behave differently for the same logical error condition
+4. **Code Complexity**: Requires custom exception handling and special-case logic
+
+## Current Implementation (Temporary Workaround)
+
+To maintain backward compatibility while fixing our test suite, we implemented a temporary solution:
+
+```java
+// ConfigConverter.java
+static class InvalidBooleanValueException extends IllegalArgumentException {
+  // Custom exception for backward compatibility
+}
+
+public static Boolean booleanValueOf(String value) {
+  // ... validation logic ...
+  throw new InvalidBooleanValueException("Invalid boolean value: " + value);
+}
+
+// ConfigProvider.java  
+catch (ConfigConverter.InvalidBooleanValueException ex) {
+  // Special case: return false instead of default for backward compatibility
+  return (T) Boolean.FALSE;
+}
+```
+
+This approach works but adds complexity and maintains the inconsistent behavior.
+
+## Proposed Solution
+
+### For Next Major Release: Standardize All Type Conversions
+
+1. **Remove Custom Boolean Logic**: Eliminate `InvalidBooleanValueException` and special handling
+2. **Consistent Exception Handling**: All invalid type conversions throw `IllegalArgumentException`
+3. **Consistent Fallback Behavior**: All types fall back to user-provided defaults
+
+### After the Change
+
+```java
+// All types will behave consistently:
+int intValue = configProvider.getInteger("key", 42);        // invalid → 42
+boolean boolValue = configProvider.getBoolean("key", true); // invalid → true  
+float floatValue = configProvider.getFloat("key", 3.14f);   // invalid → 3.14f
+```
+
+## Implementation Plan
+
+### Phase 1: Next Major Release
+- Remove `InvalidBooleanValueException` class
+- Update `ConfigConverter.booleanValueOf()` to throw `IllegalArgumentException`
+- Remove special boolean handling from `ConfigProvider.get()`
+- Update documentation and migration guide
+
+### Phase 2: Communication
+- Release notes highlighting the breaking change
+- Update configuration documentation with examples
+- Provide migration guidance for affected users
+
+## Breaking Change Impact
+
+### Who Is Affected
+- Users who rely on invalid boolean values defaulting to `false`
+- Applications that depend on the current behavior for error handling
+
+### Migration Path
+Users can adapt by:
+1. **Fixing Invalid Configurations**: Update configurations to use valid boolean values
+2. **Adjusting Defaults**: If they want `false` as fallback, explicitly set `false` as the default
+3. **Adding Validation**: Implement application-level validation if needed
+
+### Example Migration
+```java
+// Before (relied on invalid → false)
+boolean feature = configProvider.getBoolean("feature.enabled", true);
+
+// After (explicit about wanting false for invalid values)  
+boolean feature = configProvider.getBoolean("feature.enabled", false);
+```
+
+## Benefits
+
+### For Users
+- **Predictable Behavior**: Invalid values consistently fall back to provided defaults
+- **Better Debugging**: Clear error signals when configurations are invalid
+- **Explicit Intent**: Default values clearly express intended fallback behavior
+
+### For Maintainers
+- **Simplified Codebase**: Remove custom exception types and special-case logic
+- **Consistent Testing**: All type conversions can be tested with the same patterns
+- **Reduced Complexity**: Fewer edge cases and branches to maintain
+
+## Recommendation
+
+We recommend implementing this change in the next major release (e.g., v2.0) because:
+
+1. **Improves User Experience**: More predictable and debuggable configuration behavior
+2. **Reduces Technical Debt**: Eliminates custom workarounds and special cases
+3. **Aligns with Principle of Least Surprise**: Consistent behavior across all data types
+4. **Proper Breaking Change Window**: Major release is the appropriate time for behavior changes
+
+## Questions for Discussion
+
+1. Do we agree this inconsistency is worth fixing with a breaking change?
+2. Should we provide any additional migration tooling or validation?
+3. Are there other configuration behaviors we should standardize at the same time?
+4. What timeline works best for communicating this change to users?
+
+---
+
+**Next Steps**: If approved, we'll create implementation issues and begin updating documentation for the next major release cycle.

internal-api/src/test/groovy/datadog/trace/api/ConfigCollectorTest.groovy

@@ -9,6 +9,7 @@ import datadog.trace.api.config.TraceInstrumentationConfig
 import datadog.trace.api.config.TracerConfig
 import datadog.trace.api.iast.telemetry.Verbosity
 import datadog.trace.api.naming.SpanNaming
+import datadog.trace.bootstrap.config.provider.ConfigProvider
 import datadog.trace.test.util.DDSpecification
 import datadog.trace.util.Strings
 
@@ -228,4 +229,24 @@ class ConfigCollectorTest extends DDSpecification {
     "logs.injection.enabled" | "false"
     "trace.sample.rate"      | "0.3"
   }
+
+  def "config id is null for non-StableConfigSource"() {
+    setup:
+    def key = "test.key"
+    def value = "test-value"
+    injectSysConfig(key, value)
+
+    when:
+    // Trigger config collection by getting a value
+    ConfigProvider.getInstance().getString(key)
+    def settings = ConfigCollector.get().collect()
+
+    then:
+    // Verify the config was collected but without a config ID
+    def setting = settings.get(key)
+    setting != null
+    setting.configId == null
+    setting.value == value
+    setting.origin == ConfigOrigin.JVM_PROP
+  }
 }

internal-api/src/test/groovy/datadog/trace/bootstrap/config/provider/StableConfigSourceTest.groovy

@@ -1,5 +1,7 @@
 package datadog.trace.bootstrap.config.provider
 
+import datadog.trace.api.ConfigCollector
+
 import static java.util.Collections.singletonMap
 
 import datadog.trace.api.ConfigOrigin
@@ -251,7 +253,42 @@ class StableConfigSourceTest extends DDSpecification {
     }
   }
 
-  // Use this if you want to explicitly write/test configId
+  def "test config id exists in ConfigCollector when using StableConfigSource"() {
+    given:
+    Path filePath = Files.createTempFile("testFile_", ".yaml")
+    String expectedConfigId = "123"
+
+    // Create YAML content with config_id and some configuration
+    def yamlContent = """
+config_id: ${expectedConfigId}
+apm_configuration_default:
+  DD_SERVICE: test-service
+  DD_ENV: test-env
+"""
+    Files.write(filePath, yamlContent.getBytes())
+
+    // Clear any existing collected config
+    ConfigCollector.get().collect().clear()
+
+    when:
+    // Create StableConfigSource and ConfigProvider
+    StableConfigSource stableConfigSource = new StableConfigSource(filePath.toString(), ConfigOrigin.LOCAL_STABLE_CONFIG)
+    ConfigProvider configProvider = new ConfigProvider(stableConfigSource)
+
+    // Trigger config collection by getting a value
+    configProvider.getString("SERVICE", "default-service")
+
+    then:
+    def collectedConfigs = ConfigCollector.get().collect()
+    def serviceSetting = collectedConfigs.get("SERVICE")
+    serviceSetting.configId == expectedConfigId
+    serviceSetting.value == "test-service"
+    serviceSetting.origin == ConfigOrigin.LOCAL_STABLE_CONFIG
+
+    cleanup:
+    Files.delete(filePath)
+  }
+
   def writeFileRaw(Path filePath, String configId, String data) {
     data = configId + "\n" + data
     StandardOpenOption[] openOpts = [StandardOpenOption.WRITE] as StandardOpenOption[]