8000 Configu Upsert Command Missing Import Flag · Issue #728 · configu/configu · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Configu Upsert Command Missing Import Flag #728

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.

Sign up for GitHub

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

Jump to bottom
Open
LongBeachHXC opened this issue Mar 18, 2025 · 0 comments
Open

Configu Upsert Command Missing Import Flag #728

LongBeachHXC opened this issue Mar 18, 2025 · 0 comments
Labels
bug Something isn't working community triage The issue is new and needs to be triaged by a maintainer

Comments

@LongBeachHXC
Copy link
LongBeachHXC commented Mar 18, 2025 •
edited
Loading

Current Behavior

It seems the new version of the CLI is missing the --import flag on the upsert command.

This is preventing me from upgrading off of 0.17

configu --version
@configu/cli/0.17.1 wsl-x64 node-v20.10.0

configu upsert --help
Create, update or delete `Configs` from a `ConfigStore`

USAGE
  $ configu upsert --store <value> --set <value> --schema <value> [-c <value> | --import <value>]

FLAGS
  -c, --config=<value>...  'key=value' pairs to upsert. Use an empty value to delete a `Config`
      --import=<value>     Import an existing .env or flat .json file and create `Configs` from its records
      --schema=<value>     (required) `ConfigSchema` (config-keys declaration) path/to/[schema].cfgu.json file to operate the upsert against. The keys declared in the `ConfigSchema` can be assigned a value in the `ConfigSet` that will be upserted as a `Config` to the `ConfigStore`
      --set=<value>        (required) `ConfigSet` (config-values context) to assign the upserted `Configs`. Use an empty string for the root set
      --store=<value>      (required) `ConfigStore` (configs data-source) to upsert `Configs` to

./configu --version
1.2.3

./configu upsert --help
Create, update or delete `Configs` from a `ConfigStore`

$ configu upsert

━━━ Options ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  --store,--st #0     `ConfigStore` (configs data-source) to upsert `Configs` to
  --set,--se #0       `ConfigSet` (config-values context) to assign the upserted `Configs`. Use an empty string for the root set
  --schema,--sc #0    `ConfigSchema` (config-keys declaration) path/to/[schema].cfgu.json file to operate the upsert against. The keys declared in the `ConfigSchema` can be assigned a value in the `ConfigSet` that will be upserted as a `Config` to the `ConfigStore`
  --assign,--kv #0    'key=value' pairs to upsert. Use an empty value to delete a `Config`

Expected Behavior

I would expect the configu upsert command to support the --import flag like its predecessor.

To Reproduce

Download version 0.17 and execute configu upsert --help to see the option available.

Download latest version and execute configu upsert --help and you'll notice the import option gone.

Context

This makes it easier to load configuration stores with a set of values very quickly.
@LongBeachHXC LongBeachHXC added the bug Something isn't working label Mar 18, 2025
@github-actions github-actions bot added triage The issue is new and needs to be triaged by a maintainer community labels Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working community triage The issue is new and needs to be triaged by a maintainer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LongBeachHXC
0