Merge branch 'main' into iframe-setup

Author: khushisharmaharness

.github/CODEOWNERS

@@ -69,10 +69,10 @@ static/  @rohanmaharjan100 @wei-harness
 /src/components/Docs/data/continuousIntegrationData.ts @nofarblue @dewan-ahmed @SushrutHarness @shivloka-harness
 
 # CODE Docs
-/docs/code-repository/ @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10
-/release-notes/code-repository.md @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10
-/src/components/Roadmap/data/codeData.ts @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10
-/src/components/Docs/data/codeRepositoryData.tsx @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10
+/docs/code-repository/ @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10 @SushrutHarness
+/release-notes/code-repository.md @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10 @SushrutHarness
+/src/components/Roadmap/data/codeData.ts @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10 @SushrutHarness
+/src/components/Docs/data/codeRepositoryData.tsx @hitesharinga @dewan-ahmed @johannesHarness @nofarblue @atefehmohseni @rkapoor10 @SushrutHarness
 
 # STO Docs
 /docs/security-testing-orchestration/ @tejakummarikuntla @priteshchandaliya

archive/redirects/client-redirect-netlify-format-aug-23-2023.txt

@@ -637,8 +637,8 @@ https://developer.harness.io/docs/continuous-integration/ci-technical-reference/
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-to-ecr-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-ecr-step-settings
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-steps/build-and-push-to-docker-hub-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-docker-hub-step-settings
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-to-docker-hub-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-docker-hub-step-settings
-https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-steps/build-and-push-to-gcr-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-gcr
-https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-to-gcr-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-gcr
+https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-steps/build-and-push-to-gcr-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-gar
+https://developer.harness.io/docs/continuous-integration/ci-technical-reference/build-and-push-to-gcr-step-settings https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push-to-gar
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/plugin-steps/ci-bitrise-plugin https://developer.harness.io/docs/continuous-integration/use-ci/use-drone-plugins/ci-bitrise-plugin
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/ci-bitrise-plugin https://developer.harness.io/docs/continuous-integration/use-ci/use-drone-plugins/ci-bitrise-plugin
 https://developer.harness.io/docs/continuous-integration/ci-technical-reference/plugin-step-settings-reference https://developer.harness.io/docs/continuous-integration/use-ci/use-drone-plugins/plugin-step-settings-reference

docs/ai-sre/runbooks/create-runbook.md

@@ -100,6 +100,47 @@ Variables make your runbooks dynamic and reusable across different scenarios.
 
 <DocImage path={require('./static/workflow-variables.png')} width="90%" height="90%" title="Defining Workflow Variables" />
 
+#### Dynamic Parameter Selection
+
+When configuring actions, you can use dynamic parameters from various sources to make your runbooks more flexible and powerful.
+
+1. **Select an Action**: After adding an action to your workflow, configure its parameters.
+2. **Choose Dynamic Parameter Source**: For applicable fields, click the data picker icon to access dynamic data sources:
+   - **Runbook Inputs**: Variables defined in the Input/Output section.
+   - **Action Outputs**: Results from previously executed actions.
+   - **Pipeline Outputs**: Data from Harness pipeline executions.
+   - **Global Variables**: System-wide variables available to all runbooks.
+   - **Key Events**: Event-driven data that can trigger specific behaviors.
+
+<DocImage path={require('./static/dynamic-parameter-selection.png')} width="90%" height="90%" title="Selecting Dynamic Parameter Sources" />
+
+#### Key Event Integration
+
+Key Events provide a powerful way to create event-driven runbooks that respond to specific triggers.
+
+1. **Select Key Event as Source**: When configuring an action parameter, choose "Key Event" as the data source.
+2. **Create Input and Set Value**: Instead of navigating to the Input/Output section, you can create inputs directly:
+   - Click "Create Input and Set Value".
+   - Provide a Display Name, Type, and Default Value.
+   - Save the new input variable.
+   - Select the Key Event text from the input dropdown.
+
+<DocImage path={require('./static/key-event-integration.png')} width="90%" height="90%" title="Key Event Integration" />
+
+<DocImage path={require('./static/key-event-dynamic-input.png')} width="90%" height="90%" title="Key Event Dynamic Input" />
+
+#### Trigger Configuration with Key Events
+
+Once Key Events are configured in your action parameters:
+
+1. **Set Trigger Condition**: In the Triggers section, set the condition to "Key Event Created".
+2. **Map Event to Input**: The input field that was configured with the Key Event text can now be automatically populated when the trigger fires.
+3. **Dynamic Execution**: When the specified Key Event occurs, the runbook will execute with the event data automatically mapped to your configured inputs.
+
+<DocImage path={require('./static/key-event-trigger.png')} width="90%" height="90%" title="Configuring Key Event Triggers" />
+
+This approach allows for seamless integration between event detection and automated response, without requiring manual configuration of input variables for each execution.
+
 ## Step 2: Available Actions and Integrations
 
 Harness AI SRE provides a comprehensive library of pre-built actions across multiple categories. Choose the right combination of actions to build effective automation workflows.

docs/ai-sre/runbooks/static/dynamic-parameter-selection.png

@@ -0,0 +1,15 @@
+---
+hide_table_of_contents: true
+hide_title: true
+title: Application & API Posture Management
+id: application-api-posture-management
+unlisted: true
+---
+
+<!-- # Open Source -->
+
+<!-- Custom component -->
+
+import ApplicationApiPostureManagement from '@site/src/components/Docs/ApplicationApiPostureManagement';
+
+<ApplicationApiPostureManagement />

docs/ai-sre/runbooks/static/key-event-dynamic-input.png

@@ -0,0 +1,15 @@
+---
+hide_table_of_contents: true
+hide_title: true
+title: Application & Api Protection
+id: application-api-protection
+unlisted: true
+---
+
+<!-- # Open Source -->
+
+<!-- Custom component -->
+
+import ApplicationApiProtection from '@site/src/components/Docs/ApplicationApiProtection';
+
+<ApplicationApiProtection />

docs/ai-sre/runbooks/static/key-event-integration.png

@@ -0,0 +1,15 @@
+---
+hide_table_of_contents: true
+hide_title: true
+title: Application & Api Security Testing
+id: application-api-security-testing
+unlisted: true
+---
+
+<!-- # Open Source -->
+
+<!-- Custom component -->
+
+import ApplicationApiSecurityTesting from '@site/src/components/Docs/ApplicationApiSecurityTesting';
+
+<ApplicationApiSecurityTesting />