Support saved configuration for `tyger buffer` commands

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, go
Domain
cli, cloud

Research direction

The issue names no files, tests, or entry points. Start by locating the tyger buffer command implementation and its handling of --block-size and --dop; done means those values can be loaded from $XDG_CONFIG_HOME, with hostname- and operation-specific defaults if that optional configuration is supported.

Written by the indexing model from the issue text.

Description

enhancement

Save values for --block-size and --dop in a file in $XDG_CONFIG_HOME. These values, if present, would become the default.

We could also support different values per hostname:

{
    "myeastusaccount.blob.core.windows.net": {
        "read": {
            "dop": 32
        },
        "write": {
            "dop": 64",
            "blockSize": "16MiB"
        }
    },
    "mywestusaccount.blob.core.windows.net": {
        "dop": 512
        "blockSize": "4MiB"
    },
    "*": {
        "dop": 32
        "blockSize": "16MiB"
    }
}
Dominant language
Go
Stars
74
Forks
23
Avg merge
6d 16h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/tyger

All issues in microsoft/tyger

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.