Option to passthrough CTRL-C/SIGINT
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
I am using sops to start psql (PostgreSQL client) sessions.
The thing is now that psql handles CTRL-C, since it is an interactive shell by itself (e.g. just aborts editing of a commend and returning to a clean DB prompt).
When inside an sops exec-env ... 'psql -w, that behavior is broken since sops seems to handle the interrupt request and simply drops me out of the psql session.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing signal handling in the sops exec-env command and reproduce the behavior with an interactive psql session. Done means an option allows CTRL-C/SIGINT to reach psql without sops terminating the session unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100