Support converting other config files to Flow files #3659
Labels
flow
Related to Grafana Agent Flow
frozen-due-to-age
Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
As Flow gains adoption, supporting config conversions from various tools which have rough feature parity with Flow will help users migrate to Flow.
Conversion should be best-effort, if something configured in the source config does not have an equivalent in Flow, the conversion should generate either a warning or an error.
Conversion should be defined for anything that exists in Flow which has a reasonable equivalent in the source config file.
After conversion exists, we should update the PR template to remind authors to update the conversion code, if relevant to the new component.
Tasks
grafana-agent
command line for translating supported configs to river #3737run
command for translating supported configs to river on the fly #3738The text was updated successfully, but these errors were encountered: