You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2018. It is now read-only.
I would really like to fix the parsing / printing of the “fix” and “check” strings so that:
BAD: ( one long ugly but correctly escaped string )
“Using pgaudit PostgreSQL can be configured to audit various facets of PostgreSQL. See supplementary content APPENDIX-B for documentation on installing pgaudit.\n\nAll errors, denials and unsuccessful requests are logged if logging is enabled. See supplementary content APPENDIX-C for documentation on enabling logging.\n\nNote: The following instructions use the PGDATA”
GOOD: (respects \n\n and \n etc. and is wrapped at either 120 or 80 chars)
“Using pgaudit PostgreSQL can be configured to audit various facets of PostgreSQL. See supplementary content APPENDIX-B for
documentation on installing pgaudit.
All errors, denials and unsuccessful requests are logged if logging is enabled. See supplementary content APPENDIX-C for
documentation on enabling logging.
Note: The following instructions use the PGDATA”
To make the resulting inspec stubs more human readable
The text was updated successfully, but these errors were encountered:
aaronlippold
changed the title
Fix the parsing / printing of the “fix” and “check” strings
Fix the parsing / printing of the “fix” and “check”, "Title" and "Desc" strings
Apr 20, 2017
I would really like to fix the parsing / printing of the “fix” and “check” strings so that:
BAD: ( one long ugly but correctly escaped string )
“Using pgaudit PostgreSQL can be configured to audit various facets of PostgreSQL. See supplementary content APPENDIX-B for documentation on installing pgaudit.\n\nAll errors, denials and unsuccessful requests are logged if logging is enabled. See supplementary content APPENDIX-C for documentation on enabling logging.\n\nNote: The following instructions use the PGDATA”
GOOD: (respects \n\n and \n etc. and is wrapped at either 120 or 80 chars)
“Using pgaudit PostgreSQL can be configured to audit various facets of PostgreSQL. See supplementary content APPENDIX-B for
documentation on installing pgaudit.
All errors, denials and unsuccessful requests are logged if logging is enabled. See supplementary content APPENDIX-C for
documentation on enabling logging.
Note: The following instructions use the PGDATA”
To make the resulting inspec stubs more human readable
The text was updated successfully, but these errors were encountered: