Skip to content

Support non-string values in profiles #647

@LucasPickering

Description

@LucasPickering

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Right now, profile values must be templates. #646 demonstrates a need for an object value here, to be used as part of an argument to a jq call. This will help make jq a more pleasant JSON manipulation tool.

Describe the solution you'd like
A clear and concise description of what you want to happen

We can treat this similar to JSON bodies, where strings are templates and everything else is a literal value that gets stringified on demand. Template unpacking should probably not apply here though.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered

Additional context
Add any other context or screenshots about the feature request here

Metadata

Metadata

Assignees

No one assigned

    Labels

    qolImprovements that make usage smoother, without introducing new functionality

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions