Anwar Hidayat

Additional considerations that need to be included. We also need to put a glossary for every keyword we use. Another thing to add is a step-by-step guide for each possible...

closing this as it's already implemented

> @irainia salt has a printer module which provides these func. I would recommend us to use salt package for all cli outputs. Sure, we can use any required libraries,...

So far, the following is the observed relationship between job structure in various layers: ```zsh models.JobSpec (models/job.go) | |-- store.local.Job (store/local/job_spec_adapter.go) |-- store.postgres.Job (store/postgres/adapter.go) |-- [skip] api.proto.odpf.optimus.core.v1beta1.JobSpecification (api/handler/v1beta1/job_spec.go) ``` *...

### TLDR * we will have Optimus migration up and rollback only * migration up is run automatically when server up * migration rollback is run using client command, for...

When doing migration up, sometimes we encounter failure, such as from SQL syntax error. Solving this is quite tricky. If we look from the library's point of view (https://github.com/golang-migrate/migrate), we...

Also, the current pipeline failed. Try to resolve the `lint` jobs and ignore the `unite-test` one for now.

@Tharun1718333 we can have a separate discussion to resolve this, just let me know

Closing this PR as it is addressed by [this PR](https://github.com/odpf/optimus/pull/550) with some updates to also resolve the conflicts.

Result of discussion about the approach on 2022-09-21: * we expecte proto not to be changed * ~split the bigquery specific structure, such as `BQTableMetadata` into smaller one~ (update based...