Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update content/v2.0/influxdb-templates/stacks/_index.md 

Co-authored-by: Russ Savage <russorat@users.noreply.github.com>
pull/1376/head
kelseiv 2020-09-03 17:27:56 -07:00 committed by GitHub
parent c6c570f7ed
commit 4d45fb5084
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/v2.0/influxdb-templates/stacks/_index.md
View File

@ -100,7 +100,7 @@ influx apply --force true --stack-id $REDIS_STACK_ID -q
The `--json` flag in the InfluxDB CLI is very useful when scripting against the CLI, as it allows you to grab important information easily using [`jq`](https://stedolan.github.io/jq/manual/v1.6/). The `--json` flag in the InfluxDB CLI is very useful when scripting against the CLI, as it allows you to grab important information easily using [`jq`](https://stedolan.github.io/jq/manual/v1.6/).
{{% /note %}} {{% /note %}}
You can do this for each of the stacks you are maintaining. Each time you make a change to one of the resources in the stack, you can re-run this script and your changes will be applied to the resources in your InfluxDB instance. There's no need to check for changes before re-applying a stack, since re-applying the same resources doesn't change anything. You can do this for each of the stacks you are maintaining. Each time you make a change to one of the resources in the stack, you can re-run this script and your changes will be applied to the resources in your InfluxDB instance. Re-applying a stack with an updated resource won't add, delete, or duplicate resources.
For a complete example, check out the blog on [Building a GitOps Workflow with InfluxDB Templates](). For a complete example, check out the blog on [Building a GitOps Workflow with InfluxDB Templates]().