Skip to content

Commit

Permalink
Remove beta warning (#66)
Browse files Browse the repository at this point in the history
* Remove beta warning

* small cosmetic fixes
  • Loading branch information
luisquix authored Sep 5, 2024
1 parent 70f159d commit 977421c
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 9 deletions.
2 changes: 1 addition & 1 deletion docs/cli-local-secrets.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Adding the `api_secret_token` under the "Secrets" section ensures it is handled
To integrate the new secret into your pipeline, run the following command:

```bash
$ quix pipeline update
quix pipeline update
```

This command updates your pipeline configuration, incorporating the secret into the `quix.yaml` file and generating or updating the `.secrets` file:
Expand Down
6 changes: 0 additions & 6 deletions docs/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,12 +22,6 @@ Using the **cloud commands**, you can manage your Quix Cloud account from the co

With the **utility commands**, you can perform tasks such as checking your status, updating the CLI, changing the CLI configuration, using interactive help, and managing contexts (the endpoint or environment the CLI is connected to).

## Development status

!!! warning "Quix CLI is in development"

Quix CLI is currently Beta, and is under development. This documentation may not be completely up to date, as the CLI is updated frequently, with new commands added, some commands removed, and changes to command syntax. Please use the Quix CLI built-in help for the very latest information.

## GitHub repository

View additional information about the CLI in the [GitHub repository](https://github.com/quixio/quix-cli){target=_blank}.
Expand Down
4 changes: 2 additions & 2 deletions docs/yaml-reference/app-descriptor.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,9 +94,9 @@ Changes to the `app.yaml` file should be made thoughtfully, as they can affect a
## Best Practices

- **Consistent Naming:** Ensure that variable names are clear and descriptive to avoid confusion during deployment.
-

- **Security:** Handle `Secret` type variables with care to ensure sensitive information is not exposed.
-

- **Documentation:** Keep the `description` field updated to accurately reflect the purpose and usage of each variable.

By managing your `app.yaml` file effectively, you can ensure that your application is deployed consistently and operates reliably in various environments, while retaining the flexibility to adapt or remove elements as needed.

0 comments on commit 977421c

Please sign in to comment.