Skip to main content

Fix the run url in the notification policies

Feature Requests

I’ve noticed that `input.run_updated.urls.run` of a notification policy returns a URL where the ID of the run is lower case, resulting in a 404 status code when this url is visited, as the web app expects it to be upper cased. I.e. <URL 1> is returned while it should be

<URL 2> I could fiddle with it myself as a workaround but would prefer not to if at all possible.

Workaround
Problem
Status: 🗑️ Archived6 comments

Log in to comment and vote

Comments6

  • Blue Brownie

    •

    Feb 12, 2025

    Hey Ricardo. This is Peter from Spacelift engineering. Are you sure you didn’t modify the URL when processing it? I tried to reproduce this but mine is uppercase. Do you have sampling enabled? If so, can you send a sample?

    • Indigo Magnetosphere

      •

      Feb 12, 2025

      Hey, you’re right, the run ID in the URL is upper cased in the sample I’ve just checked! Weird, I must have missed some sort of manipulation in the policy, sorry for the red herring!

      EDIT: Just found the culprit - we’re pushing metrics to Datadog and any tags passed along seem to be lowercased by Datadog when they arrive. Our workaround is to pass the run ID as a tag of its own so that we can upper case it in say a Datadog monitor and use it to assemble the URL to a spacelift run

      • Natalia Gazda

        Team•

        Feb 21, 2025

        @Ricardo Azevedo Oliveira is that alright if I close the request then?

        • Indigo Magnetosphere

          •

          Feb 25, 2025

          yes feel free to

  • Indigo Magnetosphere

    •

    Jan 15, 2025

    didn’t realise this would eventually become a public post - could you please remove the urls to our spacelift space before making it public?

    • Natalia Gazda

      Team•

      Jan 15, 2025

      Hey Ricardo, the post is not public yet. And absolutely, I will remove that before making it public :)