Skip to content

[FEAT] Consider greater input encapsulation with lifecycle meta-arguments #99

@artis3n

Description

@artis3n

Is your feature request related to a problem? Please describe.

Using the module requires learning all about the GitHub OIDC token and how to combine claims to achieve your desired configuration. We have custom internal tooling to encapsulate these details, and I'd love to add encapsulation to the native properties of this module.

Describe the solution you'd like

We could allow folks to fully customize the bound_subject and additional_claims while also offering syntactic sugar in which they ask for a certain type of role, e.g. branch binding, and pass in the name of their branch, and we construct the appropriate bound_subject behind the scenes with validation using https://developer.hashicorp.com/terraform/language/expressions/custom-conditions.

Describe alternatives you've considered

This not being useful.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestterraformPull requests that update Terraform code

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions