Skip to content

AWS Config Provider: Support for metadata.links transformation #489

@Jamsre

Description

@Jamsre

🔖 Feature description

The AWS Config provider should support transforming metadata.links in addition to fields transformations. Currently, only fields (annotations, spec, etc.) can be transformed via the transform configuration.

Expected configuration:

catalog:
  providers:
    awsConfig:
      default:
        transform:
          fields:
            # existing field transformations
            links: # Add to metadata.links
              - title: "Grafana Dashboard"
                icon: "dashboard"
                url:
                  expression: '"https://grafana.example.com/d/dashboard-id/ec2-monitoring?var-instance=" & $resource.resourceId'

This would allow dynamic link generation based on resource properties, similar to how annotations work today.

🎤 Context

The AWS Config provider does not support adding links to imported resources through the transform configuration. The links section is completely ignored during transformation.

The imported AWS resources show "No links defined for this entity" in the Backstage UI, even when links are configured in the transform section.

There is no standard annotation equivalent for links like there is for other metadata fields, limiting the ability to automatically add contextual links to AWS resources.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions