Add serverless guidance for Feature Flags server SDKs#37110
Add serverless guidance for Feature Flags server SDKs#37110leoromanovsky wants to merge 2 commits into
Conversation
Preview links (active after the
|
|
|
||
| ## Public API and local evaluation | ||
|
|
||
| The public Feature Flags API is intended for managing flags and environments. It is not a per-request flag evaluation API for server-side applications. |
There was a problem hiding this comment.
[Not a blocker] Let's link to the API docs for feature flags here and/or in the "additional reading" below.
https://docs.datadoghq.com/api/latest/feature-flags/
There was a problem hiding this comment.
I can only run on private repositories.
|
Opened DOCS-14576 to follow up with editorial review. |
| DD_AGENT_HOST=<PRIVATE_AGENT_HOSTNAME_OR_IP> | ||
| DD_TRACE_AGENT_PORT=8126 | ||
| DD_REMOTE_CONFIG_ENABLED=true | ||
| DD_EXPERIMENTAL_FLAGGING_PROVIDER_ENABLED=true |
There was a problem hiding this comment.
Do "defang the snake" let's after this add a note that the "EXPERIMENTAL" word is for backwards compatibility and flags are no longer experimental.
There was a problem hiding this comment.
For this to make sense I assume you want a note everywhere this exists; that's fine. BTW dropping this prefix, I believe it's appropriate to for those SDKs where we have stable production usage, will be a nice easy test for the tool I want to build next week.
There was a problem hiding this comment.
Agree on both fronts, and my pending PR adds that note everywhere: #36573
4 participants
Motivation
Feature Flags server SDK documentation did not explain how serverless workloads receive Remote Configuration payloads. Users running on AWS Lambda, Google Cloud Run, Azure Functions, and similar platforms need clear guidance that the Datadog Agent is required for server-side flag payload delivery, and that deeper serverless support is planned for a future release.
Changes
This PR adds a new Serverless Environments guide under the Feature Flags Implementation Patterns folder. The guide explains the Agent-backed Remote Configuration flow, the recommended stateful-Agent architecture for serverless workloads, the required environment variables, operational considerations, and validation steps.
It also adds environment-specific notes for AWS Lambda, Google Cloud Run services and functions, Azure Functions, AWS Fargate/container tasks, and managed edge/function platforms. The PR adds the Implementation Patterns folder to the Feature Flags left navigation and keeps the server SDK overview linked to the serverless guidance through both inline copy and further reading.
Decisions
The guidance stays high level and architecture-focused instead of duplicating language-specific SDK setup. The page explicitly calls out that the public Feature Flags API is for management, not per-request flag evaluation, and that application-owned defaults or static configuration are outside Remote Configuration delivery when no Agent path is available.
Validation performed locally:
git diff --checkyarn run build:hugoafter generating a transient Cdocs assets partial; the serverless page rendered before the folder move, but the full build exited on existing repo-wide missing generated data sources unrelated to this change.