Set up a pre-built use case

In Kubiya, you can achieve time-to-automation in record speeds by delegating tasks from Kubiya's library of use cases.

Rapid time-to-automation, or as we call it time-to-delegation, is simple as choosing a use case from Kubiya's library, customizing it by providing the necessary parameters.

Prerequisites:

• Kubiya Runner with Healthy status (required)

  • For Kubernetes use cases, the runner must be a local runner

  • For all other use cases, the runner can be local runner or hosted runner

• Integrations (depending on your use case)

  • AWS use cases require an AWS integration, Jira use cases require a Jira integration, etc.

• Secrets (depending on your use case)

  • If your use involves a platform for which Kubiya doesn't have a native integration, add auth tokens and API keys as secrets

How to set up a use case

1. Go to the Use Cases page

In the top-bar navigation menu, click Teammates. Then in the left-hand menu, click Use Cases.

Here you can see a list of your existing use cases.

2. Click Add Use Case

Click the Add Use Case button in the top-right corner

3. Select a Use Case

Browse the various use cases that Kubiya offers out-of-the-box. Upon selecting a use case from the list, a preview of the use case will be shown on the right.

Choose the use case that best fits your needs, then click Continue.

4. Add Details

You will be presented with a form to fill in the details for the use case. Where possible, Kubiya will offer you to choose from the resources that you've already created in the Kubiya platform (e.g. integrations, runners, secrets, and more).

• Name: Give your use case a memorable nickname to easily identify it later on.

• Description: Give a clear description of what it does. This is important so that when chatting with your AI Teammates they'll know which use case you're referring to.

5. Save Details

Once all mandatory fields in the form are completed, click Save & Continue.

6. Review & Delegate

A confirmation screen will appear, listing each resource that will be created as part of the use case. This includes both Kubiya resources and third-party resources from platforms like GitHub or Jira.

If you need to make changes, just click the back arrow in the top-left corner.

If it looks good, click Delegate and Kubiya will start provisioning the resources listed in the summary.

Note: This can take up to a few minutes, so please continue to check back and/or refresh the page. You can see the use case's current status on the Use Cases list screen.

When the resources are finished provisioning, the use case's status will be Active, which means that your Kubiya Teammate can now perform the use case.

In some cases, there might be an issue. If so, the status will be Error. In this case, click on the use case to view a more detailed error message and steps to resolve it. If you're having trouble, please reach out to our team at [e-mail].

Use Case Statuses

• Provisioning: Resource provisioning is still in progress.

• Active: Resource provisioning was successful. Your use case has officially been delegated and your Kubiya Teammate can now perform it.

• Error: If Terraform Apply fails, a banner message will inform you that the use case could not be created, with a prompt to view the use case details for more information.

Sidenote: Resources created by your use case

Kubiya resources created by a use case cannot be modified from their respective resource list pages since they are managed by this use case. To modify these resources in any way, you must do it by editing the use case itself.

Using your AI Teammate