helm-chart

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

What would you like to be added:

Document experience we have seen with various log rotation size/frequency settings and how rotate_wait or refresh_interval may help.

Why is this needed:

To help users validate the upper limit of a single collector and review some deployment changes that can be made t

Describe the bug

Version number has to be changed manually.

Expected behavior

Version number changes automatically with each new release

Automation pipeline that keeps version number up to date.

Additional context

From the last Hangout.

I don't know where to start, but with some pointers maybe I can assist :).

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https

It would be nice to auto-generate the datastore_crypto_key as part of the helm install.
All of the templates get templated at once, so using the st2-generate-symmetric-crypto-key utility (as described in the datastore doc) cannot be encapsulated within the chart. Instead, we need to be able to generate the key using [he