Support Wildcard Matching for caller_id
and space_id
in Spacelift Token Join Method
#52578
Labels
c-pf
Internal Customer Reference
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
machine-id
What would you like Teleport to do?
Support wildcard values in the
caller_id
andspace_id
fields for the Spacelift token join method. This would allow for more flexible and scalable permissions management.What problem does this solve?
Currently, the allow rules in the Spacelift token object require an exact match on
caller_id
(stack) orspace_id,
which does not allow for dynamic or grouped permissions. This limitation makes it difficult for users to manage permissions across multiple stacks or environments without extensive manual configuration.For example, with wildcard support, we could define:
This would enable permissions to be granted across multiple stacks matching the pattern, such as different regions or environments, improving automation and usability.
If a workaround exists, please include it.
A possible workaround is to use
space_id
instead ofcaller_id,
but this is not a viable option in cases where Spacelift requires a one-to-one mapping of spaces to stacks. Users would need to manually create and maintain a separate space per stack, which adds unnecessary complexity. Another alternative is to explicitly list all stack names, but this is not scalable for dynamic or frequently changing environments.Adding wildcard support in
caller_id
andspace_id
would significantly improve flexibility and usability for managing Spacelift-integrated resources.Related Code & Documentation:
Teleport Spacelift Integration Docs
Relevant PR
The text was updated successfully, but these errors were encountered: