4 ms·
All AWS CLI commands follow the format 'aws [service] [action] [flags...]'. To my knowledge, there are exactly zero instances where positional arguments are use
by 015a 5y ago
All AWS CLI commands follow the format 'aws [service] [action] [flags...]'. To my knowledge, there are exactly zero instances where positional arguments are used outside of naming the service and action; its always flags.
Whether this is best or not is a different discussion; I'm simply pointing out the irony of suggesting the CLI API for a service designed to make their APIs more consistent, should be inconsistent with the other CLI APIs customers are used to.
- OJFord 5y agoYes I know, I was sort of using it (new CLI designed to be a better interface) to say why is it so. Apparently I hold a minority opinion that's so offensively contrary it deserves downvotes though! I maybe didn't make it clear enough, but I think it's somewhere between 'don't care either way' and 'great' for non-interactive/scripted use. I just don't like the UX at all for using it interactively, I find it extremely slow and cumbersome. This looks to be a big improvement, but - to me - just leaves such easy obvious trivial stuff on the table.
- chrisoverzero 5y agoRe: positional arguments, I was surprised recently to find this one (`outfile`) in the AppConfig API. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/appconfig/get-configuration.html https://awscli.amazonaws.com/v2/documentation/api/latest/ref...