{"action":"created","issue":{"url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/875","repository_url":"https://api.github.com/repos/aws-amplify/amplify-js","labels_url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/875/labels{/name}","comments_url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/875/comments","events_url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/875/events","html_url":"https://github.com/aws-amplify/amplify-js/issues/875","id":324867746,"node_id":"MDU6SXNzdWUzMjQ4Njc3NDY=","number":875,"title":"What is the best way to manage release lifecycle in Amplify?","user":{"login":"BrianSHenderson","id":2174330,"node_id":"MDQ6VXNlcjIxNzQzMzA=","avatar_url":"https://avatars0.githubusercontent.com/u/2174330?v=4","gravatar_id":"","url":"https://api.github.com/users/BrianSHenderson","html_url":"https://github.com/BrianSHenderson","followers_url":"https://api.github.com/users/BrianSHenderson/followers","following_url":"https://api.github.com/users/BrianSHenderson/following{/other_user}","gists_url":"https://api.github.com/users/BrianSHenderson/gists{/gist_id}","starred_url":"https://api.github.com/users/BrianSHenderson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BrianSHenderson/subscriptions","organizations_url":"https://api.github.com/users/BrianSHenderson/orgs","repos_url":"https://api.github.com/users/BrianSHenderson/repos","events_url":"https://api.github.com/users/BrianSHenderson/events{/privacy}","received_events_url":"https://api.github.com/users/BrianSHenderson/received_events","type":"User","site_admin":false},"labels":[{"id":708993532,"node_id":"MDU6TGFiZWw3MDg5OTM1MzI=","url":"https://api.github.com/repos/aws-amplify/amplify-js/labels/question","name":"question","color":"cc317c","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-05-21T10:34:14Z","updated_at":"2018-08-31T00:29:43Z","closed_at":"2018-07-03T21:10:32Z","author_association":"NONE","body":"Is there an efficient way to publish to testing/staging/production using Amplify?"},"comment":{"url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/comments/417510992","html_url":"https://github.com/aws-amplify/amplify-js/issues/875#issuecomment-417510992","issue_url":"https://api.github.com/repos/aws-amplify/amplify-js/issues/875","id":417510992,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNzUxMDk5Mg==","user":{"login":"jadbox","id":595843,"node_id":"MDQ6VXNlcjU5NTg0Mw==","avatar_url":"https://avatars1.githubusercontent.com/u/595843?v=4","gravatar_id":"","url":"https://api.github.com/users/jadbox","html_url":"https://github.com/jadbox","followers_url":"https://api.github.com/users/jadbox/followers","following_url":"https://api.github.com/users/jadbox/following{/other_user}","gists_url":"https://api.github.com/users/jadbox/gists{/gist_id}","starred_url":"https://api.github.com/users/jadbox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jadbox/subscriptions","organizations_url":"https://api.github.com/users/jadbox/orgs","repos_url":"https://api.github.com/users/jadbox/repos","events_url":"https://api.github.com/users/jadbox/events{/privacy}","received_events_url":"https://api.github.com/users/jadbox/received_events","type":"User","site_admin":false},"created_at":"2018-08-31T00:29:43Z","updated_at":"2018-08-31T00:29:43Z","author_association":"NONE","body":"@swaminator hey folks, I'm wondering if anything has changed related to managing lifecycles, particularly coming out of the conversations had. My main use-case currently is switching Cognito client_ids depending on the url being using, so I'm considering just overriding `aws_user_pools_web_client_id` based on my project's `.env/.staging` files that are committed in the repo. I'm not wild about committing those client_ids into the repo, but I don't see a clean way of going about this."}}
{"actor":{"display_login":"jadbox"}}