> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/configuration-standards/standardized-cli-parameters-migration.md).

# Standardized CLI Parameters Migration

### Why This Matters

SeaLights CLI parameters are now standardized across all technologies to make configuration:

* **Consistent** – same parameter = same meaning everywhere
* **Simple** – easier to learn and remember
* **Scalable** – seamless across multi-tech environments

***

### What’s Changing

All CLI parameters now follow:

* Prefix: `--`
* Format: **lower camel case**

#### Examples

| Before                       | After              |
| ---------------------------- | ------------------ |
| `-buildsessionid`            | `--buildSessionId` |
| `-appname`                   | `--appName`        |
| `-branch`                    | `--branchName`     |
| `-build`                     | `--buildName`      |
| `-workspacePath` / `-binDir` | `--scanDir`        |
| `-loglevel`                  | `--logLevel`       |
| `-failonerror`               | `--failOnError`    |

***

### Good News: No Breaking Changes

* Existing parameters **still work** (supported as aliases)
* Migration can be **gradual**
* No immediate action required

***

### Recommended Migration (3 Steps)

{% stepper %}
{% step %}

### Identify

Find where SeaLights CLI is used:

* CI/CD pipelines
* Build scripts
* Test runners
  {% endstep %}

{% step %}

### Replace

Update to standardized parameters:

```
--buildSessionId
--appName
--branchName
--buildName
--scanDir
```

{% endstep %}

{% step %}

### Validate

After updates, confirm:

* Builds complete successfully
* Coverage is reported
* Test stages are visible
  {% endstep %}
  {% endstepper %}

***

### Best Practice

* Use **only standardized parameters** for all new implementations
* Keep naming consistent across all technologies

***

### When Are You Done?

You’re fully migrated when:

* All pipelines use standardized parameters
* No legacy naming remains
* Same CLI structure across all tech stacks

***

### Need Help?

If you’re unsure how to migrate your setup, reach out to your SeaLights representative.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/configuration-standards/standardized-cli-parameters-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.