https://garden.io logo
Join Discord
Powered by
how can I completely reboot garden. I am getting t...
# 🤖｜ask-kapa
m
Please stand by @swift-spring-8620 as I search the knowledge base. I normally take about 20 seconds or so. :wave:
---------------------- Based on the information provided in the extracts, there isn't a direct solution to the error you're encountering. However, you can try the following general troubleshooting steps: 1. Ensure that you have the correct version of Garden installed. You can check your current version by running 
garden version
. 2. If you're working with a specific project, make sure you've correctly cloned the project and are in the right directory. For example, if you're working with the quickstart example, you should have cloned it with 
git clone <https://github.com/garden-io/quickstart-example.git> && cd quickstart-example
. 3. Try running 
garden dev
again. This command starts the Garden dev console, which initializes Garden and waits for further instructions. 4. If you're still encountering issues, it might be helpful to check if there are any known bugs related to your problem on the Garden GitHub issues page (). If none of these steps resolve your issue, you might want to reach out to the Garden community or support for more specific assistance. ---------------------- 
Note: you can ask me a follow up question by @ mentioning me again
:speech_balloon: ----------------------
Let me check the knowledge base for you. One moment! :books:
s
@microscopic-river-74022 is there anyway to receive inputs from the user during a workflow?
m
---------------------- Based on the provided extracts, Garden workflows allow you to define sequences of Garden commands and custom scripts. However, there's no direct mention of receiving inputs from the user during a workflow. You can define inputs in the 
ConfigTemplate
using the 
inputsSchemaPath
field, which points to a standard JSON Schema file. This schema describes the inputs for every action and module that references the template. These inputs can then be referenced using 
${inputs.*}
template strings, anywhere under the 
configs
and 
modules
fields. Here's an example of how it might look:
Copy code
json
{
  "type": "object",
  "properties": {
    "containerPort": {
      "type": "integer"
    },
    "servicePort": {
      "type": "integer"
    },
    "replicas": {
      "type": "integer",
      "default": 3
    }
  },
  "required": [
    "containerPort",
    "servicePort"
  ]
}
In this example, the 
containerPort
and 
servicePort
inputs are required, and you can optionally set a 
replicas
value as well. However, this doesn't directly allow for user input during a workflow. It's more about defining what inputs are required for the actions and modules that are part of the workflow. For more information, you can refer to the Garden documentation on Config Templates () and Workflows (). ---------------------- 
Note: you can ask me a follow up question by @ mentioning me again
:speech_balloon: ----------------------
PreviousNext
Powered by