Skip to main content

Allow multiple custom subject templates

Feature Requests

It would be helpful if it were possible to apply custom subject templates at the space level, or as contexts. That way calls coming from some spaces/stacks have different subject templates that other spaces/stacks. This would give us the flexibility to adjust the template based on customer needs instead of purely at the instance level.

Problem
Status: 🔭 Discovery2 comments

Log in to comment and vote

Comments2

  • Aleksandra Cieslak

    Team•

    Jul 27

    Hi @Connor Ries & @Adam Harvie !

    Thank you so much for the feedback, this is really helpful.

    I'd love to understand your use case for templates better. Would you be open to a short (~20–30 min) feedback call?

    If so, feel free to grab a time that works for you here:

    https://calendar.app.google/Y2PtErRYdnNDUVuJ8

    If none of the slots fit your schedule, just let me know and I'll find another time.

    Thanks again!

  • Aqua Volcano

    •

    Jul 24

    We have a similar problem: we’re integrating with multiple providers, which have varying format expectations. Example discrepancy for Snowflake:

    Snowflake is configured for exact subject:
    space:space-name-0QPKSZN38N4OUZ3YXT9NJH3FB8:stack:stack-name

    But Spacelift is sending:
    space:space-name-0QPKSZN38N4OUZ3YXT9NJH3FB8:stack:stack-name:run_type:PROPOSED:scope:read

    Snowflake does not support wildcards, so this will also break down when used in more than one stack or run_type.

    Other providers have different expectations, so allowing one provider to dictate the subject template for our whole org is a non-starter.

    This means we have to fallback on key or secrets-based auth flows. These carry an additional configuration and operational burden, especially when they require rotation.

    Being able to configure this on a stack level would allow more use of OIDC auth.