Description of problem: Because we support only http/https protocols for cloning git repositories, it makes no sense to have Private key and Private key Passphrase fields in SCM credentials form Version-Release number of selected component (if applicable): 5.8.0.15.20170517161141_119e6fd How reproducible: always Steps to Reproduce: 1. Enable Ansible Embedded role 2. Navigate to Automation - Ansible - Credentials 3. Configuration - Add new credentials, choose SCM credential type Actual results: This fields have no use, because git+ssh won't be supported by CFME UI. Expected results: Remove Private key and Private key Passphrase fields from SCM credentials form Additional info:
The embedded Ansible credentials form is completely data driven by whatever comes from backend (api). If those two fields aren't meant to be in the form (which I'm not sure is correct, I do not see this being approved by product management), this needs to be changed on the backend.
Hi James, Note this is a blocker bug for the 5.8.1 release. Thanks Bronagh
Backend doesn't impose any limitation on protocols that we support. It is UI imposing the limitation on the protocols. My recommendation would be that: since this knowledge resides in UI, the removal of these fields should stay with UI. Let me know
Jason, I'm pretty sure I recall something about not carrying the keys inside cloudforms for git access, that's why we don't support git URLs yet. If this is the case, I'm thinking the back end should not provide these fields yet until we have a solution. Hacking the front end to remove the ssh key fields doesn't seem right as, once the back end can handle the support, we won't need to remember to go back and change the UI code. I'm willing to do it on the front end, but would like your opinion. Thx, Dan
I think there is a misunderstanding from all sides here. Initially, during the requirements phase, we had wanted to avoid developing for SCM credentials, in order to pare down the problem and to fit the release time frame, so we imposed the limitation of http/https. However, during the development phase we realized that we needed the SCM credentials modeled anyway, so we went ahead with it. I spoke with James, and it is my understanding that the backend can support SSH as well as http/https. Thus, since the UI is already exposing this, SSH should just work and just needs to be tested and verified. I think the issue here is that the initial assumption of the BZ issue is invalid: > we support only http/https protocols for cloning git repositories
Pavol, can you please try to verify what Jason says above? Let me know if the UI won't allow a git type URL to be entered as we can fix that, but if it does allow it, then the SSH keys should work. Thx, Dan
https://github.com/ManageIQ/manageiq-ui-classic/pull/1557
Verified in 5.9.0.2.20171010190026_0413a06. The UI accepts ssh urls like git:jonnyfiveiq/Ansible_Playbooks, but the backend can't pull playbooks.