Max Williams

> In addition, to get the metric names the code appears to be reading pages of metric names returned until it runs into no more pages. This is the worse...

> I might experiment with https://github.com/previousnext/newrelic-exporter and see if we can just get a subset of the ones we need. Just a note about the other exporter, it also doesn't...

> For what it's worth, if there's any way of getting access to a NR API endpoint so that I can actually test changes I'd be happy to see if...

Great idea! Or also a github action would be nice 🙂

We are also plagued by this problem. I had these ideas: 1. Prepend all lines with the module name/path 2. Buffer and group the output per module and print later...

Sometime the text output of `run-all` commands is actually totally scrambled, like this for example: ``` + id = (known after apply) # module.cache.aws_cloudwatch_metric_alarm.high_database_memory_usage[0] will be created + insufficient_data_actions =...

Does this mean you are wanting helm to be able to run kubesec and decrypt the data before using it in the chart?

Cool! I am also looking for a tool to integrate with helm. One such tool is [helm-secrets](https://github.com/futuresimple/helm-secrets), I haven't used it though. Would you be aiming for some different functionality?

OK I just tested out helm-secrets. TBH I think it's too complicated. It encrypts all the values in the secret file: ``` apiVersion: ENC[AES256_GCM,data:2EY=...,type:str] kind: ENC[AES256_GCM,...,type:str] metadata: name: ENC[AES256_GCM...,type:str] ```...

I persisted with [helm-secrets](https://github.com/futuresimple/helm-secrets), now I get the kinda rigid file naming and layout. It works pretty well once you understand this and we are now using it extensively. I'm...