#2669 Banner prompt should accept y/n and incase left blank and pressed enter prompt should reappear
Closed: wontfix Opened by mharmsen.

Banner prompt should accept y/n and in case when left blank and pressed enter
prompt should reappear

Steps to Reproduce:

1.Add banner.txt to /etc/pki/<instance>/
2.run pki command
   pki -d /root/multihost_tests/certdb/ -c Secret123 -h pki1.example.com -p 8080
   -n "PKI CA Administrator for Example.Org" --ignore-cert-status
   "UNTRUSTED_ISSUER" user-del tuser1
3. prompt appears

Actual results:

If you press enter at the prompt message "Do you want to proceed(y/n)?", the
command returns to shell prompt.

Expected results:

It should reappear to accept y/n response and leave the command prompt when
used cntrl+C

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1446524
- Custom field type adjusted to defect
- Custom field version adjusted to ''

Metadata Update from @mharmsen:
- Issue priority set to: minor

Metadata Update from @mharmsen:
- Issue assigned to edewata

Metadata Update from @mharmsen:
- Issue priority set to: major (was: minor)

Metadata Update from @mharmsen:
- Issue priority set to: minor (was: major)

Per CS/DS Meeting 09/25/2017: 10.5 critical

Metadata Update from @mharmsen:
- Issue priority set to: critical (was: minor)

I think this is mostly just a preference. In general I'd like to provide a default value if possible for all questions to make it more user friendly. In this case I'd rather not pick Y as the default since the user is supposed to acknowledge the banner, so the only other option is N, which causes it to exit to the system.

Per discussion with cfu it's not necessary to change the behavior. So I'm closing this as wontfix, but feel free to reopen if there's a specific reason to change it.

Metadata Update from @edewata:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.1 (was: 10.5.0)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2789

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata