Skip to content

Commit 08c3f38

Browse files
committed
removed incorrect/outdated documentation
1 parent 24e6b2c commit 08c3f38

File tree

3 files changed

+1
-10
lines changed

3 files changed

+1
-10
lines changed

docs/reference/replicated-cli-release-lint.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Lint a directory of KOTS manifests
44

55
### Synopsis
66

7-
Lint a directory of KOTS manifests. If a `.replicated` configuration file is present, the command will automatically discover and lint resources based on the configuration. Otherwise, use `--yaml-dir` to specify the directory containing manifest files.
7+
Lint a directory of KOTS manifests.
88

99
For more information about configuring automatic resource discovery, see [.replicated Configuration File](/reference/cli-replicated-config).
1010

@@ -19,7 +19,6 @@ replicated release lint [flags]
1919
-h, --help help for lint
2020
-o, --output string The output format to use. One of: json|table (default "table")
2121
--verbose Show verbose output, including discovered images
22-
--yaml-dir yaml The directory containing multiple yamls for a Kots release. Cannot be used with the yaml flag. If omitted and a .replicated config exists, resources will be auto-discovered.
2322
```
2423

2524
### Options inherited from parent commands

docs/vendor/quick-start.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -550,10 +550,6 @@ Before you begin, do the following to set up your environment:
550550
:::note
551551
If you see a `helm-archive-missing` error, confirm that you have only one chart archive in `manifests` for version 1.0.1, and that the `chartVersion` in the HelmChart resource is also set to `1.0.1`. If you notice that any of the errors are from files in your `.history/` directory, run `rm -rf .history` and then lint the files again.
552552
:::
553-
554-
:::tip
555-
For automated workflows, you can create a `.replicated` configuration file to define your project structure, resources, and linting preferences. This enables commands like `replicated release lint` to automatically discover and process resources without the `--yaml-dir` flag. See [.replicated Configuration File](/reference/cli-replicated-config).
556-
:::
557553

558554
1. Create and promote a new release, setting the version label of the release to `0.0.2`:
559555

docs/vendor/releases-creating-cli.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,6 @@ To create and promote a release:
6161

6262
Where `PATH_TO_RELEASE_DIR` is the path to the directory with the release files.
6363

64-
:::note
65-
If you have a `.replicated` configuration file, you can run `replicated release lint` without the `--yaml-dir` flag to automatically discover and lint resources. See [.replicated Configuration File](/reference/cli-replicated-config).
66-
:::
67-
6864
For more information, see [release lint](/reference/replicated-cli-release-lint) and [Linter Rules](/reference/linter).
6965

7066
1. Do one of the following:

0 commit comments

Comments
 (0)