[RHBA-724] Added rhpam70-authoring template

[bmozaffa]

https://issues.jboss.org/browse/RHBA-724

Thanks for submitting your Pull Request!

Please make sure your PR meets the following requirements:

• Pull Request title is properly formatted: [CLOUD-XYA] Subject
• Pull Request contains link to the JIRA issue
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket
• Attached commits represent units of work and are properly formatted
• You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
• Every commit contains Signed-off-by: Your Name <yourname@example.com> - use git commit -s

[errantepiphany]

See comment on admin vs. maven user/pass in relation to RHDM-319.

[errantepiphany]

I understand why it's easier to replace the maven user/pass with the admin user/pass in these lines, because of https://issues.jboss.org/browse/RHDM-319 . However, once that jira is completed, this change will have to get reverted. So, the options are 1) keep it as maven user/pass, and people will have to continue passing in the same args for both admin and maven user/pass until RHDM-319 is fixed, or 2) make these changes here, but then have to revert them to maven user/pass once RHDM-319 is fixed. Thoughts?

[bmozaffa]

I agree that RHDM-319 is forcing us to use admin credentials to authenticate against Maven, and we would want to rectify this as soon as RHDM-319 is resolved. Until then, we have no other option. Reverting the change will just mean providing the admin credentials to the template from outside, but still having to change things around once RHDM-319 is resolved. We would then generate a Maven password that is shared across both services, but the status quo doesn't help with that anyway.

[errantepiphany]

Understood. Will now merge, and we'll have to circle back this. Thanks!