{"action":"opened","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/676","repository_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config","labels_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/676/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/676/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/676/events","html_url":"https://github.com/spring-cloud/spring-cloud-config/issues/676","id":218120871,"number":676,"title":"Native environment location locator customization request","user":{"login":"andysworkshop","id":4107468,"avatar_url":"https://avatars2.githubusercontent.com/u/4107468?v=3","gravatar_id":"","url":"https://api.github.com/users/andysworkshop","html_url":"https://github.com/andysworkshop","followers_url":"https://api.github.com/users/andysworkshop/followers","following_url":"https://api.github.com/users/andysworkshop/following{/other_user}","gists_url":"https://api.github.com/users/andysworkshop/gists{/gist_id}","starred_url":"https://api.github.com/users/andysworkshop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andysworkshop/subscriptions","organizations_url":"https://api.github.com/users/andysworkshop/orgs","repos_url":"https://api.github.com/users/andysworkshop/repos","events_url":"https://api.github.com/users/andysworkshop/events{/privacy}","received_events_url":"https://api.github.com/users/andysworkshop/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-30T08:37:05Z","updated_at":"2017-03-30T08:37:05Z","closed_at":null,"body":"Please can [this behavior](https://github.com/spring-cloud/spring-cloud-config/blob/master/spring-cloud-config-server/src/main/java/org/springframework/cloud/config/server/environment/NativeEnvironmentRepository.java#L160-L167) be made optional? We use the native environment to back the config server with an internal website which our internal deployment tools are able to manage and control. \r\n\r\nWe want the search locations that we specify to be honored in the order that we specify them so that we can implement a hierarchy of general environment properties, project-wide properties then service-specific properties in that order. This kind of works until the auto-labeling logic is hit and we get an unwanted search location tacked on.\r\n\r\nIf we could just have a property that says 'don't interfere with our search locations' then that would be great. Currently I've had to copy-paste the whole source to the native repository into my own very similar custom version. Unfortunately I can't extend the native repository because most of the member variables are private (why?)"}}
{"actor":{"display_login":"andysworkshop"}}