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

Adjust configuration options #13

Closed
tmaiaroto opened this issue Jan 13, 2016 · 1 comment
Closed

Adjust configuration options #13

tmaiaroto opened this issue Jan 13, 2016 · 1 comment

Comments

@tmaiaroto
Copy link
Owner

Allow a configuration's options (if any) to be adjusted after the configuration is created.

This is particularly useful for DynamoDB. A configuration can be created with a certain value for read and write capacity units, but then later need an increase to scale for usage.

This can be done using AWS' console of course...But that's not real convenient and maybe the credentials being used only allow access to DynamoDB - no console login. So it's super handy to be able to adjust any settings for a configuration through discfg.

When more storage options are added, like S3, then different options may be available. Though I can't see all too many being needed. I can't think of anything S3 would need... Well, maybe it can turn on/off reading from a public URL. Who knows.

Config the config =) Gotta happen.

@tmaiaroto tmaiaroto added this to the Alpha Features milestone Jan 13, 2016
@tmaiaroto
Copy link
Owner Author

This is mostly done. Just needs a refactor. The original thinking was all based around how the API would work. A simple HTTP OPTIONS request that would be both a getter and a setter. If there was a JSON body passed, then parse that and update the configuration storage options. Otherwise, just read the configuration info - which would include information about the configuration storage options.

Though it works differently from the CLI. There's less info returned to the command line for starters. Also, it doesn't make sense to have one command with an optional argument that changes the behavior of the command. There's an cfg info (also available as just info for convenience) command as well as an cfg update. So it doesn't make sense to lump the getter and setter into one function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant