AWS CLI users struggle to feed JSON from files and stdin
Developers automating AWS CLI commands want to provide JSON through pipelines or files, but stdin is not accepted for `--cli-input-json`, and the required `file://` prefix is unexpected. Confusing errors make it harder to tell whether a file path or input format is the issue.
For developers automating AWS CLI commands. Mentioned from Jun 2020 to Nov 2023 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 2.0/10
- Pain
- 4.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Low
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
I want to use aws-cli in a pipeline scenario. Therefore I want to pass as argument for --cli-input-json the value from stdin
I doubt we're going to see AWS fix this, but here's a workaround: yoursecretoutput | aws ssm put-parameter ... --value file:///dev/stdin
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks