Skip to content

docs: add disabled option in argocd #31

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
toto04 merged 1 commit into from
Mar 10, 2025
Merged

docs: add disabled option in argocd #31

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
24 changes: 24 additions & 0 deletions docs/infrastructure/03-Guides/deploy-a-new-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,3 +183,27 @@ spec:
# add-highlight-end
```
:::

## Options
These are some useful options you can configure by editing the `config.json` file.
### Disable an app
If you want to disable an app (excluding it from the git generator) you can add `"disabled": true`.
Example:
```yaml title="config.json"
{
# add-highlight-next-line
"disabled": true
"image": {
"image_list": "x/image1:latest x/image2:latest",
"update_strategy": "digest"
}
}
```

To reactivate the application just remove this property or set it to `false`.
This configuration option is introduced with [this commit](https://github.com/PoliNetworkOrg/terraform/commit/8ddf6e984c802d823573e85f147d48a916556c7c).

:::info
In the git generator configuration the selector is set to `"false"` due to the limitations of `matchExpression`.
However, in the application's `config.json` you can set the `disabled` flag to either `false` or `"false"`.
:::
Loading