Making URL regex less strict via DESTINATIONS_METADATA_PATH

[samadalishah]

Hello team,
As discussed on #733, I would like to use the DESTINATIONS_METADATA_PATH env to override the webhook destination definition. Not sure if I am doing something wrong locally but setting up the custom json doesn't work.

What I did

1. I am using the docker-compose under examples. In there I changed the metadata.json file under /config/outpost/destinations/webhook. I added below content

{
  "type": "webhook",
  "config_fields": [
    {
      "key": "url",
      "type": "text",
      "label": "Webhook URL",
      "description": "The URL to send webhook events to via HTTP POST",
      "required": true,
      "pattern": "^https?:\\/\\/[^\\s]+$"
    },
    {
      "key": "custom_headers",
      "type": "key_value_map",
      "label": "Custom Headers",
      "description": "Additional HTTP headers to include with every webhook request",
      "required": false,
      "key_placeholder": "Header name",
      "value_placeholder": "Header value"
    }
  ],
  "credential_fields": [],
  "label": "Webhook",
  "link": "https://hookdeck.com/webhooks/guides/what-are-webhooks-how-they-work",
  "description": "Send events as webhooks (HTTP POST).",
}

2. Next in compose.yaml file, for all three services, I added - ./config/outpost/destinations:/config/outpost/destinations under volumes and DESTINATIONS_METADATA_PATH: /config/outpost/destinations under environment
3. I ran the container and can see the files are mounted and the container ENV injected
4. But when I tried to create a destination with url as https://sam:123444@example.com/api/message via endpoint, it still returned 422 "config.url failed pattern validation". Also from the destination types endpoint, /api/v1/destination-types, I saw the default URL regex.

Looking forward to see if I am doing something wrong. Thank you in advance!

[alexluong]

Hi @samadalishah, thanks for sharing more info. It seems we're intentionally skipping the config/credentials value in the metadata file in the code, so this is not a viable work around it seems.

For the RegEx, we'll look into it and see if we can update the default value. Will let you know.

As for the metadata stuff, is there anything else you'd like to do?

[samadalishah]

Thank you @alexluong!
No, for my use cases, I wanted to use metadata only for the RegEx. If something comes later, I will start new discussion!
Looking forward to the new changes!✌️