PORT-8662 | PORT-7359 | Updated Launchdarkly Integration

docs/build-your-software-catalog/sync-data-to-catalog/feature-management/_launchdarkly_one_time_docker_parameters.mdx

@@ -4,6 +4,7 @@
 | `OCEAN__INTEGRATION__CONFIG__LAUNCHDARKLY_TOKEN` | The LaunchDarkly Cloud API token                                                                                      | ✅       |
 | `OCEAN__INTEGRATION__CONFIG__APP_HOST`              | Your application's host url                                                                                        | ❌       |
 | `OCEAN__INITIALIZE_PORT_RESOURCES`                  | Default true, When set to false the integration will not create default blueprints and the port App config Mapping | ❌       |
+| `OCEAN__SEND_RAW_DATA_EXAMPLES`                       | Default, true, Enable sending raw data examples from the third part API to port for testing and managing the integration mapping |  ❌   | 
 | `OCEAN__INTEGRATION__IDENTIFIER`                    | Change the identifier to describe your integration, if not set will use the default one                            | ❌       |
 | `OCEAN__PORT__CLIENT_ID`                            | Your Port client id                                                                                                | ✅       |
 | `OCEAN__PORT__CLIENT_SECRET`                        | Your Port client secret                                                                                            | ✅       |

docs/build-your-software-catalog/sync-data-to-catalog/feature-management/guides/_category_.json

@@ -0,0 +1,4 @@
+{
+    "label": "Guides",
+    "position": 1
+}

docs/build-your-software-catalog/sync-data-to-catalog/feature-management/guides/connect-launchdarkly-project-to-service.md

@@ -0,0 +1,114 @@
+import PortTooltip from "/src/components/tooltip/tooltip.jsx"
+
+# Connect Launchdarkly Feature Flag to a service
+
+This guide aims to cover how to connect a Launchdarkly `flag` to an existing service in Port.
+
+:::tip Prerequisites
+
+- This guide assumes you have a Port account and that you have finished the [onboarding process](/quickstart). We will use the `Service` blueprint that was created during the onboarding process.
+- Ensure you have [Launchdarkly installed and configured](/build-your-software-catalog/sync-data-to-catalog/feature-management/launchdarkly.md#installation) in your environment.
+
+:::
+
+<br/>
+
+### Add Tags to feature flags in Launchdarkly
+
+[Tagging flags in LaunchDarkly](https://docs.launchdarkly.com/home/account/tags#flags) allows you to categorize and filter them. You can use tags to group flags that are related to a specific service or feature. In this guide, we will add a tag to indicate what service the flag is related to:
+
+1. **Log in to LaunchDarkly** as a user with the necessary permissions to manage flags.
+2. **Navigate to the flags list.**
+3. **Click on the name of the flag** you want to add tags to. The flag's Targeting tab appears.
+4. **Click on the `Settings` tab.**
+5. **In the "Settings for all environments section**, select a tag or create a new tag from the Tags menu.
+5. **Add a tag** that represents the service the flag is related to, `port-auth-service`.
+6. **Click save**
+
+For this guide, let's assume there is a service entity identified by `auth-service` in your `Service` blueprint in Port.
+
+<img src='/img/guides/launchdarklyAddTagToFeatureFlag.png' width='60%' border='1px' />
+
+:::note Control the tag name
+Since our Launchdarkly `flag` may already have several tags, we will need a mechanism to control how these tags will be related to our `Service` blueprint. A way to achieve this relation is to prefix the tag name with the keyword `port-`. We will then use JQ to select the tags that starts with this keyword. So, our example tag will be named `port-auth-service`, which will correspond to a Service entity identified by `auth-service` in Port.
+:::
+
+### Create the service relation
+
+Now that Port is synced with our Launchdarkly resources, let's reflect the Launchdarkly flag in our services to display the issue associated with a service.
+First, we will need to create a [relation](/build-your-software-catalog/customize-integrations/configure-data-model/relate-blueprints/) between our services and the corresponding Launchdarkly feature flag.
+
+1. Head back to the [Builder](https://app.getport.io/settings/data-model), choose the `Launchdarkly flag` <PortTooltip id="blueprint">blueprint</PortTooltip>, and click on `New relation`:
+
+<img src='/img/guides/launchdarklyAddRelationToFlag.png' width='60%' border='1px' />
+
+<br/><br/>
+
+2. Fill out the form like this, then click `Create`:
+
+<img src='/img/guides/launchdarklyCreateServiceRelation.png' width='60%' border='1px' />
+
+<br/><br/>
+
+Now that the <PortTooltip id="blueprint">blueprints</PortTooltip> are related, we need to assign the relevant Launchdarkly Flags to each of our services. This can be done by adding some mapping logic. Go to your [data sources page](https://app.getport.io/settings/data-sources), and click on your Launchdarkly integration:
+
+<img src='/img/guides/launchdarklyIntegrationDataSources.png' border='1px' />
+<br/><br/>
+
+Under the `resources` key, modify the mapping for the `flag` kind by using the following YAML block. Then click `Save & Resync`:
+
+<details>
+<summary><b>Relation mapping (Click to expand)</b></summary>
+
+```yaml
+  - kind: flag
+    selector:
+      query: 'true'
+    port:
+      entity:
+        mappings:
+          identifier: .key + "-" + .__projectKey
+          title: .name
+          blueprint: '"launchDarklyFeatureFlag"'
+          properties:
+            kind: .kind
+            description: .description
+            creationDate: .creationDate / 1000 | strftime("%Y-%m-%dT%H:%M:%SZ")
+            clientSideAvailability: .clientSideAvailability
+            temporary: .temporary
+            tags: .tags
+            maintainer: ._maintainer.email
+            deprecated: .deprecated
+            variations: .variations
+            customProperties: .customProperties
+            archived: .archived
+          relations:
+            project: .__projectKey
+            service: .tags | map(select(startswith("port"))) | map(sub("port-"; ""; "g")) | .[0]
+```
+
+</details>
+
+:::tip JQ explanation
+
+The JQ below selects all labels that start with the keyword `port`. It then removes "port-" from each label, leaving only the part that comes after it. It then selects the first match, which is equivalent to the service in Port.
+
+```yaml
+service: .tags | map(select(startswith("port"))) | map(sub("port-"; ""; "g")) | .[0]
+```
+
+:::
+
+What we just did was map the `Launchdarkly flag` to the relation between it and our `Services`.  
+Now, if our `Service` identifier is equal to the Launchdarkly flag tag, the `service` will automatically be linked to it &nbsp;🎉
+
+<img src='/img/guides/launchdarklyFeatureFlagAfterServiceMapping.png' width='80%' border='1px' />
+
+### Conclusion
+
+By following these steps, you can seamlessly connect a Launchdarkly flag with an existing service blueprint in Port using flag tags.
+
+More relevant guides and examples:
+
+- [Port's Launchdarkly integration](/build-your-software-catalog/sync-data-to-catalog/feature-management/launchdarkly/)
+- [Toggle Launchdarkly Feature Flag](/actions-and-automations/setup-backend/github-workflow/examples/Launchdarkly/toggle-launchdarkly-feature-flag)