CLIs for plugin

[rootwarp]

Checklist

• New Feature for the Service/Plugin (Vatz)
• Enhancement (Vatz)
• others(etc. e.g, documentation, project policy management)

---

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. such as Ex. I'm always frustrated

Describe the solution you'd like| Ex

A clear and concise description of what you want to happen

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you have considered.

Additional context or comment

Add any other context or screenshots about the feature request here.

Child Issues

• Plugin install feature through CLI #298
• List plugin #320
• Use hash value for primary key of plugin DB #323
• Handle duplicated plugin install #321
• Logging plugin's log #322
• Install specific version of plugin
• Update plugin
• Enable and Disable selected plugin -> Need more discussion
• Manage plugin home by config file
• Support DB migration if the DB schema is changed
• Check VATZ is running when the plugin command is executed
• Write document for CLI usage. #350
• Store plugin's executing information #388

[gnongs]

@rootwarp I think we need to synchronize plugin information with DB and yaml file

How do you think about that ?

[rootwarp]

@rootwarp I think we need to synchronize plugin information with DB and yaml file

How do you think about that ?

@gnongs Agree. As you know plugin information is managed by two part, yaml and DB so it will make confusion to users.

But now, we have no detail plans regarding to config yaml file. So we have to estimate plan precisely to keep backward compatibility.

It could be good to make this issue public and discuss together.

@xellos00 How do you think?

[xellos00]

@rootwarp I think we need to synchronize plugin information with DB and yaml file
How do you think about that ?

@gnongs Agree. As you know plugin information is managed by two part, yaml and DB so it will make confusion to users.

But now, we have no detail plans regarding to config yaml file. So we have to estimate plan precisely to keep backward compatibility.

It could be good to make this issue public and discuss together.

@xellos00 How do you think?

@rootwarp @gnongs
Yes, I agree. It really good idea.
I prefers discuss it after we finishes node exporter and version 1.0

[rootwarp]

@xellos00 Maybe Support DB migration if the DB schema is changed item might be related what you said.

[xellos00]

t DB migration if the DB schema is

Yes, it does, Let me separate an issue and no one have trouble to update DB schema.