Merge branch 'main' into DIGCS-1-migrate-bibucket-to-github

Author: erioluwadivine

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/advanced-form-configurations.md

@@ -233,9 +233,13 @@ values={[
 
 <TabItem value="visible">
 
-The `visible` property is used to dynamically hide/show inputs in the form.
+The `visible` property is used to dynamically hide/show elements in the form.
 The `visible` value could be set to either a boolean (`true` value is always shown, `false` value is always hidden), or to a `jqQuery` which evaluates to a boolean.
 
+<h4>Input-level visibility</h4>
+
+You can apply `visible` to individual inputs to control their display:
+
 In this example, the `runArguments` properties are configured with `visible` so that they only show up in the form when the matching value is selected in the `language` input:
 
 <Tabs
@@ -318,6 +322,59 @@ action = Action(
 
 </Tabs>
 
+<h4>Step-level visibility</h4>
+
+You can also apply `visible` to entire steps to control their display:
+
+In this example, the `AWS Configuration` and `Azure Configuration` steps are conditionally shown based on the values selected in the first step's cloud provider input:
+
+<Tabs
+defaultValue="api"
+values={[
+{label: 'API', value: 'api'}
+]}>
+
+<TabItem value="api">
+
+```json showLineNumbers
+  {
+    "userInputs": {
+      "properties": {
+        "enum": {
+          "icon": "DefaultProperty",
+          "title": "Cloud provider",
+          "type": "array",
+          "items": {
+            "enum": [ "aws", "azure" ],
+            "enumColors": { "aws": "red", "azure": "blue" },
+            "type": "string"
+          }
+        }
+      },
+      "required": [],
+      "steps": [
+        {
+          "title": "Cloud selection",
+          "order": [ "enum" ]
+        },
+        {
+          "title": "AWS configuration",
+          "order": [],
+          "visible": { "jqQuery": ".form.enum | index(\"aws\") != null" }
+        },
+        {
+          "title": "Azure configuration",
+          "order": [],
+          "visible": { "jqQuery": ".form.enum | index(\"azure\") != null" }
+        }
+      ]
+    }
+  }
+```
+</TabItem>
+
+</Tabs>
+
 </TabItem>
 
 <TabItem value="dependsOn">

docs/actions-and-automations/setup-backend/webhook/port-execution-agent/usage.md

@@ -22,7 +22,6 @@ For example:
 ```json showLineNumbers
 { "type": "WEBHOOK", "agent": true, "url": "URL_TO_API_INSIDE_YOUR_NETWORK" }
 ```
-
 :::
 
 Well Done! **Port Agent** is now running in your environment and will trigger any webhook that you've configured (for self-service actions, or changes in the software catalog).
@@ -56,7 +55,7 @@ env:
     VAR_NAME: VAR_VALUE
 ```
 
-###  Proxy configuration
+### Proxy configuration
 
 #### `HTTP_PROXY`, `HTTPS_PROXY` & `ALL_PROXY`
 `HTTP_PROXY`, `HTTPS_PROXY`, and `ALL_PROXY` are environment variables used to specify a proxy server for handling HTTP, HTTPS, or all types of requests, respectively. The values assigned to these settings should be the URL of the proxy server.
@@ -81,7 +80,15 @@ For more information take a look at the Requests [proxy configuration documentat
 
 ### SSL Environment Configuration
 
-#### `REQUESTS_CA_BUNDLE`
+### Certificate Configuration
+
+#### Self-signed certificate
+
+Use the following Helm values:
+- Set `selfSignedCertificate.enabled` to `true`.
+- Put your PEM-encoded CA content in `selfSignedCertificate.certificate`.
+
+The certificate should be mounted to `/usr/local/share/ca-certificates/`.
 
 `REQUESTS_CA_BUNDLE` is an environment variable used to specify a custom Certificate Authority (CA) bundle for verifying SSL/TLS certificates in HTTPS requests.
 
@@ -94,6 +101,16 @@ REQUESTS_CA_BUNDLE=/path/to/cacert.pem
 
 This configuration directs the `requests` library to use the specified CA bundle for SSL/TLS certificate verification, overriding default system settings. It's useful for trusting self-signed certificates or certificates from a private CA.
 
+#### Multiple certificates
+
+Use the following Helm values:
+- Keep your certificate via `selfSignedCertificate` as above.
+- Add other certificates by supplying files via `extraVolumes` and mounting them with `extraVolumeMounts` into the container at `/usr/local/share/ca-certificates/<your-cert-name>.crt`.
+
+:::info Certificate file requirements
+- Each certificate must be provided in a separate PEM file. Files containing multiple certificates are not supported.
+- Certificates must be mounted to `/usr/local/share/ca-certificates/` with a `.crt` file extension.
+:::
 
 ## Next Steps
 

docs/ai-interfaces/ai-agents/_category_.json

@@ -1,4 +1,4 @@
 {
   "label": "AI agents",
-  "position": 1
+  "position": 5
 }