(template-like response) Changes in this pull request look to be in good state. Delays in other features in this project will result in this feature being delayed (see this comment for more details), so the expected window for this feature is planned around end-of-year (2019). Feel free to make additional changes/etc. to this pull request before the planned window. Critical changes may occur on master before this pull request is merged in -- while you are free to help synchronize features as conflicts are detected, I do mind help correcting conflicts myself when I have the opportunity to merge this change in. If you wish to review changes I may stack on this pull request set, feel free to indicate so. When the window to merge this in this pull requests occurs and changes are needed, I can stack on change and wait for your additional approval. Otherwise, I will assume I may stack changes (if needed) which is deemed best for this extension for a quicker integration into master. Labeling this pull request as "planned-end-of-year".

A quick review of this pull request include the following:

• The change looks good. I will most likely tweak the configuration documentation for confluence_ask_user to be independent description (instead of referencing confluence_ask_password).
• It maybe nice to adjust the input request in confluence_ask_user's use case to reflect the "default" user if one is set but an empty string is provided (i.e. input(' User [current-user-conf]: '); which is silently does with this current implementation).

Changes implemented.

@fernandogargiulo1986, thanks for the feature change. I'll just make a tweak on a feature branch and queue it up for master.