{"action":"closed","issue":{"url":"https://api.github.com/repos/ind9/gocd-s3-artifacts/issues/23","repository_url":"https://api.github.com/repos/ind9/gocd-s3-artifacts","labels_url":"https://api.github.com/repos/ind9/gocd-s3-artifacts/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/ind9/gocd-s3-artifacts/issues/23/comments","events_url":"https://api.github.com/repos/ind9/gocd-s3-artifacts/issues/23/events","html_url":"https://github.com/ind9/gocd-s3-artifacts/issues/23","id":131372693,"number":23,"title":"RRS as default Storage Class?","user":{"login":"haimizrael","id":7175841,"avatar_url":"https://avatars.githubusercontent.com/u/7175841?v=3","gravatar_id":"","url":"https://api.github.com/users/haimizrael","html_url":"https://github.com/haimizrael","followers_url":"https://api.github.com/users/haimizrael/followers","following_url":"https://api.github.com/users/haimizrael/following{/other_user}","gists_url":"https://api.github.com/users/haimizrael/gists{/gist_id}","starred_url":"https://api.github.com/users/haimizrael/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haimizrael/subscriptions","organizations_url":"https://api.github.com/users/haimizrael/orgs","repos_url":"https://api.github.com/users/haimizrael/repos","events_url":"https://api.github.com/users/haimizrael/events{/privacy}","received_events_url":"https://api.github.com/users/haimizrael/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-04T14:59:25Z","updated_at":"2016-02-10T05:51:17Z","closed_at":"2016-02-10T05:51:17Z","body":"We started using the ind9 s3 plugins a few months ago, and were unpleasantly surprised change #14 came in the 1.0.29 patch release. \r\nWe do not want to use RSS, and have 3 issues with this change:\r\n\r\n1. There is no option to turn this off and use Standard redundancy (unless one forks the code)\r\n\r\n1. It is a breaking change, not a bug-fix, so including it in a patch release could cause users of the plugin to miss the fact their artifacts suddenly start getting stored in lower redundancy\r\n\r\n1. It could have been made backward compatible for existing users of the plugin (leave the Standard storage class by default, and set an alternate storage class with a parameter - environment variable - wherever the s3.publish plugin)\r\n\r\nWe have a fork (GCM Grosvenor), where we've added 2 features: (optional) ability to encrypt uploaded artifacts with KMS, and (optional) ability to zip archive contents prior to upload to reduce latency in case of many files being uploaded), as well as fixing a couple of bugs.  The presence of this change #14 prevents us from issuing a pull request and contributing to the common code, without making our own breaking change to this feature.  \r\n\r\nPlease consider the 3 points above and advise whether you'd be open to making this feature somehow backward compatible.\r\n"}}