{"action":"created","issue":{"url":"https://api.github.com/repos/fusor/fusor/issues/13","labels_url":"https://api.github.com/repos/fusor/fusor/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/fusor/fusor/issues/13/comments","events_url":"https://api.github.com/repos/fusor/fusor/issues/13/events","html_url":"https://github.com/fusor/fusor/pull/13","id":57994222,"number":13,"title":"fusor server: initial content management actions","user":{"login":"bbuckingham","id":1319246,"avatar_url":"https://avatars.githubusercontent.com/u/1319246?v=3","gravatar_id":"","url":"https://api.github.com/users/bbuckingham","html_url":"https://github.com/bbuckingham","followers_url":"https://api.github.com/users/bbuckingham/followers","following_url":"https://api.github.com/users/bbuckingham/following{/other_user}","gists_url":"https://api.github.com/users/bbuckingham/gists{/gist_id}","starred_url":"https://api.github.com/users/bbuckingham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bbuckingham/subscriptions","organizations_url":"https://api.github.com/users/bbuckingham/orgs","repos_url":"https://api.github.com/users/bbuckingham/repos","events_url":"https://api.github.com/users/bbuckingham/events{/privacy}","received_events_url":"https://api.github.com/users/bbuckingham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-17T22:42:06Z","updated_at":"2015-02-19T14:02:42Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/fusor/fusor/pulls/13","html_url":"https://github.com/fusor/fusor/pull/13","diff_url":"https://github.com/fusor/fusor/pull/13.diff","patch_url":"https://github.com/fusor/fusor/pull/13.patch"},"body":"This commit does a few things:\r\n\r\n- Adds a config file (fusor.yaml) that will need to be placed in\r\n  foreman/config/settings.config.d to specify properties that\r\n  are needed to support the content managment actions.  These\r\n  are settings that a user should not need to touch; however,\r\n  using settings is much better than hard-coding within the plugin\r\n  logic.\r\n\r\n- Adds a 'deploy' action & route on the deployments controller.\r\n\r\n- Adds a dynflow action 'deploy' to trigger the other dynflow actions\r\n  that we need to support creating the deployment.  The actions added\r\n  so far support only following needed for content management:\r\n  - enable repositories (based upon fusor.yaml)\r\n  - sync repositories\r\n  - create composite content view (e.g. \"fusor\")\r\n  - create rpm component content view (e.g. \"fusor rpm content\")\r\n  - publish rpm component content view\r\n  - add the rpm and puppet (e.g. \"fusor puppet content\") component\r\n    content views to the composite view\r\n  - publish and promote the composite content view\r\n\r\nNote: This commit does not currently support importing manifest.\r\nIt also has several \"TODO\" items to update it to use the information\r\nin the deployment object, once available."},"comment":{"url":"https://api.github.com/repos/fusor/fusor/issues/comments/75056086","html_url":"https://github.com/fusor/fusor/pull/13#issuecomment-75056086","issue_url":"https://api.github.com/repos/fusor/fusor/issues/13","id":75056086,"user":{"login":"bbuckingham","id":1319246,"avatar_url":"https://avatars.githubusercontent.com/u/1319246?v=3","gravatar_id":"","url":"https://api.github.com/users/bbuckingham","html_url":"https://github.com/bbuckingham","followers_url":"https://api.github.com/users/bbuckingham/followers","following_url":"https://api.github.com/users/bbuckingham/following{/other_user}","gists_url":"https://api.github.com/users/bbuckingham/gists{/gist_id}","starred_url":"https://api.github.com/users/bbuckingham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bbuckingham/subscriptions","organizations_url":"https://api.github.com/users/bbuckingham/orgs","repos_url":"https://api.github.com/users/bbuckingham/repos","events_url":"https://api.github.com/users/bbuckingham/events{/privacy}","received_events_url":"https://api.github.com/users/bbuckingham/received_events","type":"User","site_admin":false},"created_at":"2015-02-19T14:02:42Z","updated_at":"2015-02-19T14:02:42Z","body":"@isratrade, Unfortunately, the deployment api code is only in the develop branch, so I cannot PR these changes alone and it doesn't look like your PR to master is including them either.  A few options:\r\n1. I pull those deployment api/model commits in to this PR\r\n2. @jmrodri or I create a separate PR to master.  \r\n3. @jmrodri  creates a separate PR to master that represents the current working view of the deployment api/model (i.e. the things you have been working).\r\n\r\nOptions 2 & 3 would require that the code changes in this PR wait until the deployment changes are in master.  That said, I tend to lean towards 3 as it could mean cleaning up the git tree and also allows for the latest changes to go in.\r\n\r\n@jmrodri, Thoughts?"}}