Currently, one secret collector and analyser per key needs to be created. This can unnecessarily inflate the Preflight resource yml.
Describe the feature
Secret collectors should have an additional optional field "keys" or, alternatively, the current "key" should allow a (comma-delimited?) list of keys.
https://troubleshoot.sh/docs/collect/secret/#key-optional
Describe alternatives you've considered
It would be possible to use Helm to generate the required collectors/analysers automatically, but this is not always an option. Plus the resulting file would still be rather verbose.
Additional context
It is possible to collect all secrets using includeAllData:true. However, collecting just a subset is currently not possible and even with all data included, you would still need one analyser per secret.
Currently, one secret collector and analyser per key needs to be created. This can unnecessarily inflate the Preflight resource yml.
Describe the feature
Secret collectors should have an additional optional field "keys" or, alternatively, the current "key" should allow a (comma-delimited?) list of keys.
https://troubleshoot.sh/docs/collect/secret/#key-optional
Describe alternatives you've considered
It would be possible to use Helm to generate the required collectors/analysers automatically, but this is not always an option. Plus the resulting file would still be rather verbose.
Additional context
It is possible to collect all secrets using
includeAllData:true. However, collecting just a subset is currently not possible and even with all data included, you would still need one analyser per secret.