feat: Add data-lineage overview

[robnewman]

Add overview page for why data lineage is important and how to access.

@netlify /platform-cloud/data/data-lineage

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	0fef4a1
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/69fa3832638242000890de65
😎 Deploy Preview	https://deploy-preview-1383--seqera-docs.netlify.app/platform-cloud/data/data-lineage
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[christopher-hakkaart]

I've made a range of suggestions to make it more concise.

I wasn't sure the exact status of "Lineage ID" vs "lineage ID". Please confirm and I can update those.

[christopher-hakkaart]

Looking good - approved, but please check the latest suggestions are correct.

[gavinelder]

Note Lineage requires additional IAM permissions beyond our current documented set for the AWS credentials used with Seqera Platform.

If a customer is using an existing AWS Batch Queue or AWS Cloud Compute Environments with custom IAM roles, they will also need to update the relevant service role policies.

For the service role they need to add

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "ListObjectsInBucket",
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket"
            ],
            "Resource": "arn:aws:s3:::seqera-lineage-<workspace-id>"
        },
        {
            "Sid": "AllObjectActions",
            "Effect": "Allow",
            "Action": "s3:*Object",
            "Resource": "arn:aws:s3:::seqera-lineage-<workspace-id>/*"
        },
        {
            "Sid": "AllowObjectTagging",
            "Effect": "Allow",
            "Action": [
                "s3:PutObjectTagging",
                "s3:GetObjectTagging"
            ],
            "Resource": "arn:aws:s3:::seqera-lineage-<workspace-id>/*"
        }
    ]
}

The Seqera Platform integration credentials require the following additional permissions.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sqs:CreateQueue",
                "sqs:GetQueueAttributes",
                "sqs:SetQueueAttributes",
                "sqs:GetQueueUrl",
                "sqs:ReceiveMessage",
                "sqs:DeleteMessage"
            ],
            "Resource": "arn:aws:sqs:*:*:seqera-lineage-*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:CreateBucket",
                "s3:GetBucketNotificationConfiguration",
                "s3:PutBucketNotificationConfiguration",
                "s3:GetBucketLocation"
            ],
            "Resource": "arn:aws:s3:::seqera-lineage-*"
        }
    ]
}

[ewels]

The new page was not included in any navigation sidebar, so was impossible to find. I've just pushed a commit to add it to the docs sidebar, hope that's ok!

'cc @robnewman @christopher-hakkaart

[ewels]

Couple of minor comments, but generally LGTM!

[justinegeffen]

@robnewman, I'm happy with this editorially. Thank you!

[georgi-seqera]

Do Seqera Platform labels propagate to lineage records?
I tried this and I don't think they do propagate to the record (only the Nextflow lineage labels were there as far as I can see)

[robnewman]

Will test to make sure

[robnewman]

Per @bentsherman , provided the Nextflow version used is 26.04, then Seqera Platform labels propagate to the lineage WorkflowRun record.

[robnewman]

And according to @swampie, the default Nextflow version in v26.1 will be 26.04, so it will be supported.

[bebosudo]

@robnewman could we move the extra policy required for lineage into the AWS Batch and AWS Cloud docs pages? Having them in a separate place like now means customers need to remember to visit the lineage page and extract the policies required whenever they create a new user, which is prone to errors and makes management harder for us. Happy to review or help.

[robnewman]

@robnewman could we move the extra policy required for lineage into the AWS Batch and AWS Cloud docs pages? Having them in a separate place like now means customers need to remember to visit the lineage page and extract the policies required whenever they create a new user, which is prone to errors and makes management harder for us. Happy to review or help.

Sure - please create a PR!