Skip to content

Add additional context to Inquiries #3952

Open
@Mierdin

Description

@Mierdin

A user in Slack mentioned he would like to be able to store additional useful information that can help inform a response to an inquiry. The use case is that core.ask is used before applying a terraform plan - it would be nice if the user could get prompted with the output from terraform plan before they have to respond to the inquiry. Right now the only way to do this is to place the output into the datastore and then look it up in a notification workflow that responds to an inquiry trigger.

I still firmly believe that the ID and route are the only fields that should be in the inquiry trigger. It's more RBAC-friendly. But we could consider adding a field to the inquirer runner for storing useful context like this. Users can see this field after retrieving the full inquiry via the API, as they have to do today to see other fields like the schema.

Should also add an st2.get_inquiry or similar action, to make it easier to retrieve inquiry details.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions