Skip to content

Update Replicated CLI docs for v0.123.0 #3710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
paigecalvert merged 1 commit into from
Dec 12, 2025
Merged

Update Replicated CLI docs for v0.123.0 #3710

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/reference/replicated-cli-release-create.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,21 @@ Create a new release
Create a new release by providing application manifests for the next release in
your sequence.

If no flags are provided, the command will automatically use the configuration from
.replicated file in the current directory (or parent directories). The config should
specify charts and manifests to include. Charts will be automatically packaged using
helm, and manifests will be collected using glob patterns.

Example .replicated config:
appSlug: "my-app"
charts:
- path: ./chart
manifests:
- ./manifests/*.yaml

With this config, simply run:
replicated release create --version 1.0.0 --promote Unstable

```
replicated release create [flags]
```
Expand Down
26 changes: 22 additions & 4 deletions docs/reference/replicated-cli-release-download.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,25 +4,43 @@ Download application manifests for a release.

### Synopsis

Download application manifests for a release to a specified directory.
Download application manifests for a release to a specified file or directory.

For KOTS applications:
- Downloads release as a .tgz file if no RELEASE_SEQUENCE specified
- Can specify --channel to download the current release from that channel
- Auto-generates filename as app-slug.tgz if --dest not provided

For non-KOTS applications, this is equivalent to the 'release inspect' command.

If no app is specified via --app flag, the app slug will be loaded from the .replicated config file.

```
replicated release download RELEASE_SEQUENCE [flags]
replicated release download [RELEASE_SEQUENCE] [flags]
```

### Examples

```
# Download latest release as autoci.tgz
replicated release download

# Download specific sequence
replicated release download 42 --dest my-release.tgz

# Download current release from Unstable channel
replicated release download --channel Unstable

# Download to directory (KOTS only with sequence)
replicated release download 1 --dest ./manifests
```

### Options

```
-d, --dest string Directory to which release manifests should be downloaded
-h, --help help for download
-c, --channel string Download the current release from this channel (case sensitive)
-d, --dest string File or directory to which release should be downloaded. Auto-generated if not specified.
-h, --help help for download
```

### Options inherited from parent commands
Expand Down