Store plugin's executing information

[rootwarp]

Checklist

• [X] New Feature for the SVC/Plugin
• [ ] New Feature for CI/CD
• [ ] Enhancement on Vatz

• [ ] Others(etc. e.g, documentation,...)

Please describe, what it's about or related Problem with

A clear description of what feature need to be developed or enhanced in Vatz

When a plugin is executed, executing information should be managed in SQLite for maintenance reason.

Describe the output that you are expecting for above

A clear and concise description of what you expect to happen.

• When the plugin is started, PID will be stored in SQLite.
• When VATZ is started, it will check plugin processes by stored PID and update DB.
• PID will be used to stop the plugin.

Describe alternatives you've considered

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

N/A

Additional context

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

[rootwarp]

@xellos00 As you know, we are not storing executing information of the plugin. And I think it could be better to store and track information at the DB.

For the starting point, I'll track the PID of the plugin. Do you have any other ideas to store?

[xellos00]

@rootwarp Guess that's best idea, no matter what I think it's a requirement to set up DB. but Let's have a meeting at some point. I will ping you. for more discussions.

[xellos00]

Plugin info - config - DB

---

• AS-IS VATZ get <- Config

• To-BE Config push -> DB VATZ get <- DB

CLI STOP, KILL
enable/disable

@meetrick Good to see through DB get .

[xellos00]

Plugin info - config - DB

• AS-IS VATZ get <- Config
• To-BE Config push -> DB VATZ get <- DB

CLI STOP, KILL enable/disable

@meetrick Good to see through DB get .

Let's put a vote.

• AS-IS 👍🏽
• To-BE ❤️

[xellos00]

Plugin info - config - DB

• AS-IS VATZ get <- Config
• To-BE Config push -> DB VATZ get <- DB

CLI STOP, KILL enable/disable @meetrick Good to see through DB get .

Let's put a vote.

• AS-IS 👍🏽
• To-BE ❤️

Output by vote

To-BE Config push -> DB VATZ get <- DB

[xellos00]

@rootwarp As we previously vote, I will take this issue to migration feature config.yaml.

[xellos00]

Tasks

• [x] Store Config.yaml into DB
• [ ] Update DB schema from previous version to New Schema
• [ ] Update VATZ to read every config value from DB

[xellos00]

1. Yaml 파일에 있는 것은 DB 에 넣지 않는다. 1.1 각 Config yaml은 따로 DB 에 저장하지 않는다. 1.2 추후에 각 사용성과 기능을 생각해 다시 회의를 진행한다.

---

@xellos00

• Plugin_info Schema Update
• Enable/Disable CLIs

---

@rootwarp & @xellos00

• Delete CLI process
• DB Migration.