feat(datadog): Request secrets update from DDAgent#1778
Conversation
Request secrets update from Core Agent if secrets are enabled and transactions fail with 403s. When we use secrets, keys might become stale because of a rotation, so we want to retry the transactions later with fresh keys. To not to wait too long (and to avoid bloating of the retry queue) we add a new RPC call to request secrets update from our Core Agent. This commit is complement to DataDog/datadog-agent#51480. Signed-off-by: Mark Kirichenko <mark.kirichenko@datadoghq.com>
|
Binary Size Analysis (Agent Data Plane)Baseline: 22dc41f · Comparison: 7a5a764 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (35)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
DRAFT: DO NOT MERGE
Summary
Request secrets update from Core Agent if secrets are enabled and transactions fail with 403s.
When we use secrets, keys might become stale because of a rotation, so we want to retry the transactions later with fresh keys. To not to wait too long (and to avoid bloating of the retry queue) we add a new RPC call to request secrets update from our Core Agent.
Change Type
How did you test this PR?
Add tests to cover the new functionality.
E2E test with complementary changes in Datadog Agents were not done yet.
References
additional_endpointsAPI keys not refreshed dynamically at runtime #1540This commit is complement to DataDog/datadog-agent#51480.