Merge branch 'master' into brett.blue/config-visibility

Author: drichards-87

README.md

@@ -43,7 +43,7 @@ Make sure all files are lowercase. Macs are case-insensitive when creating links
 
 ## Releasing
 
-Merging to `master` triggers an automatic deployment. This process typically begins within 10 minutes and usually takes around 35 minutes to complete, though these times may vary. 
+Merging to `master` triggers an automatic deployment. This process typically begins within 10 minutes and usually takes around 35 minutes to complete, though these times may vary.
 
 ## How to add a new integration
 

config/_default/menus/main.en.yaml

@@ -1112,11 +1112,6 @@ menu:
       parent: ide_plugins
       identifier: ide_plugins_vscode
       weight: 702
-    - name: Visual Studio
-      url: developers/ide_plugins/visual_studio/
-      parent: ide_plugins
-      identifier: ide_plugins_visual_studio
-      weight: 703
     - name: Community
       url: developers/community/
       parent: dev_tools
@@ -2908,11 +2903,16 @@ menu:
       parent: app_builder_components
       identifier: app_builder_custom_charts
       weight: 701
+    - name: React Renderer
+      url: actions/app_builder/components/react_renderer/
+      parent: app_builder_components
+      identifier: app_builder_react_renderer
+      weight: 702
     - name: Tables
       url: actions/app_builder/components/tables/
       parent: app_builder_components
       identifier: app_builder_tables
-      weight: 702
+      weight: 703
     - name: JavaScript Expressions
       url: actions/app_builder/expressions/
       parent: app_builder
@@ -2960,6 +2960,12 @@ menu:
       parent: datastores
       identifier: auth
       weight: 4
+    - name: Forms
+      url: actions/forms/
+      pre: file-wui
+      parent: actions_heading
+      identifier: forms
+      weight: 50000
     - name: Action Catalog
       url: actions/actions_catalog/
       pre: books
@@ -7131,31 +7137,31 @@ menu:
       url: /security/code_security/static_analysis/generic_ci_providers/
       parent: sec_static_analysis
       weight: 3
-    - name: Static Code Analysis (SAST) rules
-      identifier: sec_static_analysis_rules
-      url: /security/code_security/static_analysis/static_analysis_rules/
-      parent: sec_static_analysis
-      weight: 5
-    - name: SAST Custom Rules
-      identifier: sec_static_analysis_custom_rules
-      url: /security/code_security/static_analysis/custom_rules/
+    - name: AI-Enhanced Static Code Analysis
+      identifier: sec_static_analysis_ai
+      url: /security/code_security/static_analysis/ai_enhanced_sast/
       parent: sec_static_analysis
-      weight: 5
+      weight: 5     
     - name: SAST Custom Rule Creation Tutorial
       identifier: sec_static_analysis_custom_rules_tutorial
       url: /security/code_security/static_analysis/custom_rules/tutorial/
       parent: sec_static_analysis
-      weight: 5
+      weight: 6
+    - name: SAST Custom Rules
+      identifier: sec_static_analysis_custom_rules
+      url: /security/code_security/static_analysis/custom_rules/
+      parent: sec_static_analysis
+      weight: 7
     - name: SAST Custom Rules Guide
       identifier: sec_static_analysis_custom_rules_guide
       url: /security/code_security/static_analysis/custom_rules/guide/
       parent: sec_static_analysis
-      weight: 5
-    - name: Malicious PR Protection
-      identifier: sec_static_analysis_malicious_pr_protection
-      url: /security/code_security/static_analysis/malicious_pr_protection
+      weight: 8
+    - name: Static Code Analysis (SAST) rules
+      identifier: sec_static_analysis_rules
+      url: /security/code_security/static_analysis/static_analysis_rules/
       parent: sec_static_analysis
-      weight: 4
+      weight: 9
     - name: Software Composition Analysis (SCA)
       identifier: software_composition_analysis
       url: /security/code_security/software_composition_analysis/
@@ -7176,6 +7182,11 @@ menu:
       url: /security/code_security/software_composition_analysis/setup_runtime/compatibility/
       parent: sca_setup_runtime
       weight: 1
+    - name: Library Inventory
+      identifier: sca_library_inventory
+      url: /security/code_security/software_composition_analysis/library_inventory/
+      parent: software_composition_analysis
+      weight: 3
     - name: Secret Scanning
       identifier: sec_secret_scanning
       url: /security/code_security/secret_scanning/

content/en/account_management/billing/ci_visibility.md

@@ -19,9 +19,9 @@ This guide provides a non-exhaustive list of billing considerations for [CI Visi
 
 A committer is an active Git contributor, identified by their Git author email address. For billing purposes, a committer is included if they make at least three commits in a given month.
 
-## Charges for commits made by bots or actions performed in the GitHub UI
+## Billing for commits made by bots or actions performed in the GitHub UI
 
-Datadog does not charge for bot or commits resulting from actions made in the GitHub UI. These types of commits are excluded from billing calculations.
+Commits made by verified bots or through actions performed directly in the GitHub UI are not billed by Datadog. These are automatically excluded from billing calculations. Only verified bots are excluded from billing.
 
 ## Excluding commits from specific people
 

content/en/account_management/scim/_index.md

@@ -52,10 +52,6 @@ If you use an application key tied to a user to enable SCIM and that user leaves
 
 To avoid losing access to your data, Datadog strongly recommends that you create a [service account][6] dedicated to SCIM. Within that service account, create an application key to use in the SCIM integration.
 
-## Email verification
-
-Creating a new user with SCIM triggers an email to the user. For first time access, you are required to log in through the invite link shared by email. The link is active for 2 days. If it expires, go to the [user settings page][7] and select a user to resend an invite link.
-
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}

content/en/account_management/teams/manage.md

@@ -50,16 +50,36 @@ From the settings dialog, use the menu to customize the following team settings:
 
 ## Team membership
 
-To differentiate members of your team, designate them as team managers. In the member list, a "TEAM MANAGER" badge appears next to team managers' names.
+### Team manager
 
-Under the team's settings, specify which users can modify the team membership. The following options are available:
+To differentiate members of your team, designate some of them as team managers. In the member list, a "TEAM MANAGER" badge appears next to team managers' names.
+
+### Team modification permissions
+
+Under the team's settings, in the **Permissions** tab, specify which users can modify the team membership. The following options are available:
 - Only users with the `user_access_manage` permission
 - Team managers
 - Team managers and members
 - Anyone in the organization
 
+The list is sorted in order of increasing permissiveness. Each option in the list includes the group in the entries above it. For example, selecting "team managers" means that both team managers and users with `user_access_manage` can modify membership.
+
+The option that you select for which users can add and remove members determines whether you can add the team to access control lists. Two types of teams exist: invite only teams and open teams.
+
+Invite only teams
+: Teams with restricted membership. Can be set as access control recipients. Created when you restrict team membership modification to one of the first three options.
+
+Open teams
+: Teams with unrestricted membership. Cannot be set as access control recipients. Created when you allow **Anyone in the organization** to modify team membership.
+
 Users with the `user_access_manage` permission can set default rules on who can add or remove members, or edit team details. Set default rules with the **Default Settings** button on the team directory page. Override these policies for an individual team on the team details panel.
 
+### Teams managed outside Datadog
+
+In some cases, a team's membership cannot be directly modified within Datadog by anyone (including a user with `user_access_manage`):
+- If your org has selected SAML as the only team provisioning source, then the SAML team mappings control team membership. You cannot modify the team membership through Datadog.
+- If a team is managed through an identity provider, then the identity provider controls team membership. You cannot modify the team membership through Datadog.
+
 ### Subteams (hierarchical teams)
 
 With subteams, you can nest teams within each other to mimic your company's hierarchy in Datadog, allowing for a more complete and accurate ownership model. Subteams also provide an enhanced filtering experience; select a larger team (like a director-level group) to find all the data connected to any of its subteams.

content/en/actions/agents/_index.md

@@ -11,7 +11,7 @@ further_reading:
   text: "What are AI agents and how do they work?"
 ---
 
-{{< callout url="https://app.datadoghq.com/actions/agents" btn_hidden="false" header="Join the Preview!" >}}
+{{< callout url="https://www.datadoghq.com/product-preview/agent-builder/" btn_hidden="false" header="Join the Preview!" >}}
 Agents are in Preview. Click <b>Request Access</b> and fill in the Datadog Product Preview Program form.
 {{< /callout >}}
 

content/en/actions/app_builder/components/_index.md

@@ -657,6 +657,54 @@ Displays property and value pairs in JSON format.
 
 
 
+{{% collapse-content title="React renderer" level="h3" %}}
+React renderer components have the following properties.
+
+### General
+
+React Component Definition
+: The code that is executed to create a React component.<br>
+
+Component Input Props
+: The props that are passed to the React component and can be accessed in the props object of the component.
+
+Initial Component State
+: Sets the initial state values for your component. This state is used when the component first renders or if no state has been set yet. The component can access this data through <code>props.state</code>.<br>
+
+### Appearance
+
+Is Visible
+: Determines whether the component is visible to the end-user. In edit mode, all components remain visible.<br>
+**Provided values**: on, off
+
+### Events
+Event
+: **Values**: set component state, callback function
+
+Function Name
+: **Value**: <code>props.customFunctionName</code>
+
+Reaction
+: **Values**: close modal, custom, download file, open modal, open side panel, close side panel, set component state, set state variable value, toast notification, trigger action
+
+For more information on events, see [Events][1].
+
+### Inspect data
+
+Displays property and value pairs in JSON format.
+
+### Relationships
+
+Displays data dependencies between React renderer and components in the app.
+
+### Example
+
+For an example showing how to use this component, see [React renderer][11].
+
+{{% /collapse-content %}}
+
+
+
 {{% collapse-content title="Search" level="h3" %}}
 Search components have the following properties.
 
@@ -1174,3 +1222,4 @@ To view this component in context, see the [Metrics Explorer & Monitors Builder]
 [8]: https://www.markdownguide.org/basic-syntax/
 [9]: /service_management/app_builder/events/#state-functions
 [10]: /service_management/app_builder/components/custom_charts/
+[11]: /actions/app_builder/components/react_renderer/

content/en/actions/app_builder/components/react_renderer.md

@@ -0,0 +1,68 @@
+---
+title: React Renderer
+description: Render custom React components by defining component code, input props, and the initial component state.
+disable_toc: false
+further_reading:
+- link: "/actions/app_builder/components/"
+  tag: "Documentation"
+  text: "Components"
+- link: "/actions/app_builder/build/"
+  tag: "Documentation"
+  text: "Build Apps"
+---
+
+The React renderer enables users to create fully custom UI components using the language and libraries they already know. This component gives builders access to [React APIs][1] so they can create flexible, dynamic, and visually impactful apps in App Builder.
+
+This page provides an example of how to use the React renderer component. For a full reference to all of the fields in the React renderer, see [Components][2].
+
+## Example component definition
+
+```js
+const App = (props) => {
+  // Local component state
+  const [localState, setLocalState] = React.useState(0);
+  
+  // Access shared state from props
+  const { count = 0 } = props.state;
+  
+  const incrementShared = () => {
+  // Update shared state that persists outside component
+        
+props.setComponentState({...props.state, count: count + 1});
+};
+  
+  return (
+    <div>
+      <h3>Shared Count: {count}</h3>
+      <button onClick={incrementShared}>Increment Shared</button>
+    </div>
+);
+}
+return App;
+```
+
+### Example component input props 
+```json
+${{
+  queryData: query0.outputs,
+  name: global?.user?.name,
+  state: self.state,
+}}
+```
+
+### Example initial component state 
+```json
+${{
+  count: 0,
+  items: [],
+  isLoading: false,
+  selectedId: null,
+}}
+```
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://react.dev/reference/react/apis
+[2]: /actions/app_builder/components/#general-11