Paralus all in one cli tool about paralus HOT 2 OPEN

@akshay196
I'd like to work on this issue.
Can you assign it to me?

from paralus.

Some todos/notes:

1. Create user document for supporting different commands by Paralus (eg. paralus serve, parlaus migrate etc.)
2. Instead of migrate CLI, use migrate library in Go code. Decide where to pull migration files from. migrate support different sources. If we use migrate as library then io/FS or filesystem make sense but keep source configurable to user.
3. Keep initialization and migration separate.
4. Initialization script is using flag. main.go is using viper. Both should use single method for consistency.
5. Each command can located into separate package for example cmd/migrate for migrate, cmd/sync for oidc synchronizer. If yes, how to invoke each command from single entry (main.go at root dir)? Need library like cobra or just calling each package for respective paralus command is enough? Which one is maintainable and scalable option?
6. Support Paralus config (future need as there could be many customization options)

There are few items from above list which is not expected out of this issue, but let's keep this in mind so that we take right approach/tool for future needs.

from paralus.