Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config.toml rework, Default Values, chain details lookup #465

Open
danbryan opened this issue Sep 2, 2023 · 0 comments
Open

config.toml rework, Default Values, chain details lookup #465

danbryan opened this issue Sep 2, 2023 · 0 comments
Assignees
Labels
2023 enhancement New feature or request

Comments

@danbryan
Copy link
Collaborator

danbryan commented Sep 2, 2023

I would like to be able to simplify some of these kube jobs. For example, take job-osmosis-index-epoch-day

    [log]
    level = "info"
    pretty = true

    [base]
    api = "http://x.x.x.x:1317"

    # index transactions
    index-chain = false
    # start-block = 11220706
    start-block = 11245200
    end-block = -1

    # Block Events
    index-block-events = false
    block-events-start-block = 8732500
    block-events-end-block = -1

    # Osmosis Epoch Indexing
    index-epoch-events = true
    epoch-indexing-identifier="day"
    epoch-events-start-epoch=803
    epoch-events-end-epoch=806

    rpc-workers = 4
    throttling = 1.25005
    block-timer = 1000
    wait-for-chain = false
    reindex = false
    prevent-reattempts = false
    wait-for-chain-delay = 5
    exit-when-caught-up = false
    dry = false

    [lens]
    rpc = "http://x.x.x.x:26657"
    account-prefix = "osmo"
    chain-id = "osmosis-1"
    chain-name = "osmosis"

    [database]
    host = "x.x.x.x"
    port = "5432"
    database = "db"
    user = "user"
    password = "password"
    log-level = "error"

to this

    [base]
    api = "http://x.x.x.x:1317"

    # Osmosis Epoch Indexing
    index-epoch-events = true
    epoch-indexing-identifier="day"
    epoch-events-start-epoch=803
    epoch-events-end-epoch=806

    [lens]
    rpc = "http://x.x.x.x:26657"
    account-prefix = "osmo"
    chain-id = "osmosis-1"
    chain-name = "osmosis"

    [database]
    host = "x.x.x.x"
    port = "5432"
    database = "db"
    user = "user"
    password = "password"

The goal is to make config.toml easier to read and know what its doing. I think we should also be able to infer the account prefix, chain-id, chainname from the RPC /API server. No need to have it in the config.toml.

@danbryan danbryan added enhancement New feature or request 2023 labels Sep 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2023 enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

2 participants