{"action":"created","issue":{"url":"https://api.github.com/repos/osiam/osiam/issues/35","labels_url":"https://api.github.com/repos/osiam/osiam/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/osiam/osiam/issues/35/comments","events_url":"https://api.github.com/repos/osiam/osiam/issues/35/events","html_url":"https://github.com/osiam/osiam/issues/35","id":108494365,"number":35,"title":"How should we use YAML configuration?","user":{"login":"tkrille","id":5213491,"avatar_url":"https://avatars.githubusercontent.com/u/5213491?v=3","gravatar_id":"","url":"https://api.github.com/users/tkrille","html_url":"https://github.com/tkrille","followers_url":"https://api.github.com/users/tkrille/followers","following_url":"https://api.github.com/users/tkrille/following{/other_user}","gists_url":"https://api.github.com/users/tkrille/gists{/gist_id}","starred_url":"https://api.github.com/users/tkrille/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tkrille/subscriptions","organizations_url":"https://api.github.com/users/tkrille/orgs","repos_url":"https://api.github.com/users/tkrille/repos","events_url":"https://api.github.com/users/tkrille/events{/privacy}","received_events_url":"https://api.github.com/users/tkrille/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/osiam/osiam/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-09-26T20:44:21Z","updated_at":"2015-09-28T07:00:20Z","closed_at":null,"body":"With Spring Boot arrived in all services, we can now think about how we should use and structure the YAML-based configuration files. There are several question arising:\r\n\r\n1. What namespace should we use for OSIAM's configuration properties? I'm in favor for `org.osiam.[service name].[property]`, i.e.\r\n\r\n    ```yaml\r\n    org.osiam.auth-server:\r\n      resource-server-home: http://localhost:8080/osiam-resource-server\r\n      ldap.enabled: false\r\n    ```\r\n\r\n2. Should we wrap Spring configuration properties, i.e.\r\n\r\n    ```yaml\r\n    org.osiam.spring.session-timeout: 240\r\n    ```\r\n    or just use the ones from Spring and let ops define additional ones if they need them?\r\n\r\n3. Do we plan for a smooth transition of `.properties` files to YAML files, supporting both for some time (this might have an impact on 1. and 2.)?\r\n\r\nWhat do you think? Any other questions on your minds?"},"comment":{"url":"https://api.github.com/repos/osiam/osiam/issues/comments/143656077","html_url":"https://github.com/osiam/osiam/issues/35#issuecomment-143656077","issue_url":"https://api.github.com/repos/osiam/osiam/issues/35","id":143656077,"user":{"login":"sputnik27","id":2292245,"avatar_url":"https://avatars.githubusercontent.com/u/2292245?v=3","gravatar_id":"","url":"https://api.github.com/users/sputnik27","html_url":"https://github.com/sputnik27","followers_url":"https://api.github.com/users/sputnik27/followers","following_url":"https://api.github.com/users/sputnik27/following{/other_user}","gists_url":"https://api.github.com/users/sputnik27/gists{/gist_id}","starred_url":"https://api.github.com/users/sputnik27/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sputnik27/subscriptions","organizations_url":"https://api.github.com/users/sputnik27/orgs","repos_url":"https://api.github.com/users/sputnik27/repos","events_url":"https://api.github.com/users/sputnik27/events{/privacy}","received_events_url":"https://api.github.com/users/sputnik27/received_events","type":"User","site_admin":false},"created_at":"2015-09-28T07:00:20Z","updated_at":"2015-09-28T07:00:20Z","body":"Because @wallner mentioned it here: [This gist](https://gist.github.com/sputnik27/35b755c2b1e243fc70a9) shows how I could imagine such a migration script. It is of course not \"done\" yet, it is merely a proof of concept. I leave this here as a request for comments.\r\n\r\nAnd I won't be mad if we choose not to use it. It was just a nice chance to play with that nifty programming language called \"groovy\" :+1: "}}