# Digibeectl syntax Digibeectl uses the GET and SET commands so that you can easily configure your customer. The information is automatically saved in a configuration file, which uses the format below with the following commands: ``` digibeectl [command] [subcommand | resource] [flags] ``` * `command:` specifies the operation that you want to perform on one or more resources. For example **completion**, **config**, **create**, **delete**, **get**, **help**, **info**, **set**, **update**, **version**. * `subcommand:` specifies a specific action or category within a command that further refines the operation. For example, in the config command, you might have subcommands like **set**, **get**, **view**, **list**, **use**, **delete**. * `resource:` specifies resource to be accessed. For example api-mgmt-credentials, api-mgmt-url, config, deployment, deployment-history, pipeline. * `flags:` specifies optional flags. For example, you can use the -e or --environment to filter deployments by environment (default "test"). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.digibee.com/documentation/developer-guide/development-cycle/digibeectl/digibeectl-syntax.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.