Another bash script to power up|down aiven services using service tags#71
Another bash script to power up|down aiven services using service tags#71olivierhuber-aiven wants to merge 1 commit intoaiven:mainfrom
Conversation
|
@lornajane - what do you think about this from Olivier. An example of why you might want to tag Aiven services? |
| @@ -0,0 +1,101 @@ | |||
| #!/bin/bash | |||
|
|
|||
| # jq needs to be installed https://stedolan.github.io/jq/ | |||
There was a problem hiding this comment.
Would this (or a smaller version of it?) be useful in the USAGE output? For those folks like me who just download and run things :)
There was a problem hiding this comment.
I like this idea! A bit like Git that says "no no but you might have wanted to write this instead?" ;)
| done | ||
|
|
||
| echo "Turning [$POWER] services for project [$PROJECT] tagged [$TAG_ENV]" | ||
|
|
There was a problem hiding this comment.
There are services that either have complete data loss (e.g. Kafka) or run the risk of partial data loss (e.g. Redis) when being powered off. Is a confirmation dialog that acknowledges this risk important here?
There was a problem hiding this comment.
Oh right! Why not. Let's go for a confirmation dialog then!
|
I really like the start sequence as a reason to tag services, it's a nice real-world use case! @olivierhuber-aiven would you consider writing this as a blog post with explanation and the |
|
Thanks @lornajane |
This is bash script exemple to power up|down aiven services in a defined order|sequence using services tags

The service tags could look like this in the Aiven console: