ids

[nicolasparada]

Add method to list plugin IDs. This is usefull for autocompletion on the CLI.

Addresses part of: https://github.com/calyptia/go-fluentbit-config/issues/55

[patrick-stephens]

By ID is this the (super unsafe - fun times with non-determinism in config maps for me!) tail.0 style IDs?

[pwhelan]

By ID is this the (super unsafe - fun times with non-determinism in config maps for me!) tail.0 style IDs?

I also agree... I think we should add some level of determinism by aliasing (adding an alias property) to inputs by name in the cli and/or core-ui before we try and actually linked to this sort of thing in the CLI. I think it might even be OK to autogenerate aliases with what we guesstimate their ID to be.

Where is it going to be used @nicolasparada?

[nicolasparada]

@pwhelan there is a function in Cloud that can make use of it: https://github.com/calyptia/cloud/blob/536435cb62556ffb2bf7ddba770acec50d47d388/config_parser.go#L471 (for trace sessions).

Also in the CLI was a TODO to change using the name of the plugin, for the ID: https://github.com/calyptia/cli/blob/dba6ed005df11bfe17d6c5cd6a8b3f7c3b6f5d13/completer/completer.go#L286 (for trace sessions too).

[nicolasparada]

@patrick-stephens yes, check the tests.

[patrick-stephens]

I think we should add some level of determinism by aliasing (adding an alias property)

Can you raise an issue for this @pwhelan ? It's a very important requirement I think - without aliases it's pretty useless I found for any large scale deployment as metrics cannot be relied on, alerts cannot be fired and it just is confusing between even pods sharing the same config map getting different ids.

[jasmingacic]

The code looks good.
Other than that I'd address remarks that Pat has