{"action":"created","issue":{"url":"https://api.github.com/repos/ManageIQ/manageiq/issues/5643","labels_url":"https://api.github.com/repos/ManageIQ/manageiq/issues/5643/labels{/name}","comments_url":"https://api.github.com/repos/ManageIQ/manageiq/issues/5643/comments","events_url":"https://api.github.com/repos/ManageIQ/manageiq/issues/5643/events","html_url":"https://github.com/ManageIQ/manageiq/issues/5643","id":119507324,"number":5643,"title":"Creating and editing provider should use model's business logic","user":{"login":"Ladas","id":1737058,"avatar_url":"https://avatars.githubusercontent.com/u/1737058?v=3","gravatar_id":"","url":"https://api.github.com/users/Ladas","html_url":"https://github.com/Ladas","followers_url":"https://api.github.com/users/Ladas/followers","following_url":"https://api.github.com/users/Ladas/following{/other_user}","gists_url":"https://api.github.com/users/Ladas/gists{/gist_id}","starred_url":"https://api.github.com/users/Ladas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ladas/subscriptions","organizations_url":"https://api.github.com/users/Ladas/orgs","repos_url":"https://api.github.com/users/Ladas/repos","events_url":"https://api.github.com/users/Ladas/events{/privacy}","received_events_url":"https://api.github.com/users/Ladas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-11-30T14:49:47Z","updated_at":"2015-12-01T10:57:18Z","closed_at":null,"body":"As discussed in \r\nhttps://github.com/ManageIQ/manageiq/pull/5297\r\nhttps://github.com/ManageIQ/manageiq/pull/5639\r\n\r\nRight now, we cannot leverage methods like @evm.supports_port? and default values per provider in form for creating provider, cause it doesn't talk back to server when provider type is changed. (it's broken also in the non angular code, that talks to server)\r\n\r\nProposed solution:\r\n1. On change of provider, we will get server request that will instantiate correct Provider class, so we can use model logic to show capabilities/default values\r\n2. Just doing this in the angular form and changing infra provider form to angular"},"comment":{"url":"https://api.github.com/repos/ManageIQ/manageiq/issues/comments/160934526","html_url":"https://github.com/ManageIQ/manageiq/issues/5643#issuecomment-160934526","issue_url":"https://api.github.com/repos/ManageIQ/manageiq/issues/5643","id":160934526,"user":{"login":"himdel","id":289743,"avatar_url":"https://avatars.githubusercontent.com/u/289743?v=3","gravatar_id":"","url":"https://api.github.com/users/himdel","html_url":"https://github.com/himdel","followers_url":"https://api.github.com/users/himdel/followers","following_url":"https://api.github.com/users/himdel/following{/other_user}","gists_url":"https://api.github.com/users/himdel/gists{/gist_id}","starred_url":"https://api.github.com/users/himdel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/himdel/subscriptions","organizations_url":"https://api.github.com/users/himdel/orgs","repos_url":"https://api.github.com/users/himdel/repos","events_url":"https://api.github.com/users/himdel/events{/privacy}","received_events_url":"https://api.github.com/users/himdel/received_events","type":"User","site_admin":false},"created_at":"2015-12-01T10:57:18Z","updated_at":"2015-12-01T10:57:18Z","body":"@martinpovolny haven't done a pr yet, but the basic functionality is quite simple.. But I'm a bit worried about different lifetimes of the session and token, and I'll need some info about the sso login option and autologging.. And starting to wonder whether adding a session based authentication to the api wouldn't be a better choice. Or alternatively adding a \"give me a token to fit my session\" to the old api. "}}