)]}'
{"api/v3/identity-api-v3.rst":[{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"4983ec1642807b79098a4bea24e52bd5f6973900","unresolved":false,"context_lines":[{"line_number":900,"context_line":"- ``name`` (string)"},{"line_number":901,"context_line":""},{"line_number":902,"context_line":"  Unique project name, within the owning domain. A project name for a project"},{"line_number":903,"context_line":"  acting as a domain must be unique across all domains. Starting with version"},{"line_number":904,"context_line":"  3.7, the name includes the path to the root of any project hierarchy, not"},{"line_number":905,"context_line":"  including the project acting as a domain."},{"line_number":906,"context_line":""},{"line_number":907,"context_line":"Optional attributes:"},{"line_number":908,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_043963f2","line":905,"range":{"start_line":903,"start_character":56,"end_line":905,"end_character":42},"updated":"2016-05-31 19:43:59.000000000","message":"so I worry about this...what happens if I don\u0027t have a role on one of these parents...should I be able to see their names?","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"541f1de17b2abf14b7ade4fe8ef704f55efc4064","unresolved":false,"context_lines":[{"line_number":900,"context_line":"- ``name`` (string)"},{"line_number":901,"context_line":""},{"line_number":902,"context_line":"  Unique project name, within the owning domain. A project name for a project"},{"line_number":903,"context_line":"  acting as a domain must be unique across all domains. Starting with version"},{"line_number":904,"context_line":"  3.7, the name includes the path to the root of any project hierarchy, not"},{"line_number":905,"context_line":"  including the project acting as a domain."},{"line_number":906,"context_line":""},{"line_number":907,"context_line":"Optional attributes:"},{"line_number":908,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_077a0577","line":905,"range":{"start_line":903,"start_character":56,"end_line":905,"end_character":42},"in_reply_to":"9abb7d3a_043963f2","updated":"2016-05-31 19:47:55.000000000","message":"I remember that we had this discussion a few releases ago. One of the suggestions was, only show the names from the projects with role on it like. ProjectX.*.*.*.ProjectB","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"a1cd6e839be271d271b427211398bd6f16c27815","unresolved":false,"context_lines":[{"line_number":900,"context_line":"- ``name`` (string)"},{"line_number":901,"context_line":""},{"line_number":902,"context_line":"  Unique project name, within the owning domain. A project name for a project"},{"line_number":903,"context_line":"  acting as a domain must be unique across all domains. Starting with version"},{"line_number":904,"context_line":"  3.7, the name includes the path to the root of any project hierarchy, not"},{"line_number":905,"context_line":"  including the project acting as a domain."},{"line_number":906,"context_line":""},{"line_number":907,"context_line":"Optional attributes:"},{"line_number":908,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_078045f6","line":905,"range":{"start_line":903,"start_character":56,"end_line":905,"end_character":42},"in_reply_to":"9abb7d3a_077a0577","updated":"2016-05-31 19:54:55.000000000","message":"but if ProjectB is no longer unique in the hierarchy, that\u0027s ambigious....(which is why I\u0027m starting to like https://review.openstack.org/#/c/310048/ a bit more!)","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"ab51907f10dfc8f1d820663e7af6f4f5e259a98f","unresolved":false,"context_lines":[{"line_number":949,"context_line":"  project are immediately invalidated. Re-enabling a project does not re-enable"},{"line_number":950,"context_line":"  pre-existing tokens."},{"line_number":951,"context_line":""},{"line_number":952,"context_line":"- ``leaf_name`` (string) *New in version 3.7*"},{"line_number":953,"context_line":""},{"line_number":954,"context_line":"  Represents the name of the project node in the hierarchy, as opposed to the"},{"line_number":955,"context_line":"  ``name`` attribute that includes the path to the root project. ``leaf_name``"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_246bccf2","line":952,"range":{"start_line":952,"start_character":2,"end_line":952,"end_character":15},"updated":"2016-05-31 18:05:32.000000000","message":"think this can be a bit confusing for projects which are not leafs. Example:\n\n  A -\u003e B -\u003e C\n\nB\u0027s leaf_name would be B, right? I can totally imagine someone thinking that it would be C.","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"53851c06bf17ce6338119a14a71a754bf4ca3f71","unresolved":false,"context_lines":[{"line_number":949,"context_line":"  project are immediately invalidated. Re-enabling a project does not re-enable"},{"line_number":950,"context_line":"  pre-existing tokens."},{"line_number":951,"context_line":""},{"line_number":952,"context_line":"- ``leaf_name`` (string) *New in version 3.7*"},{"line_number":953,"context_line":""},{"line_number":954,"context_line":"  Represents the name of the project node in the hierarchy, as opposed to the"},{"line_number":955,"context_line":"  ``name`` attribute that includes the path to the root project. ``leaf_name``"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_ef7a3df0","line":952,"range":{"start_line":952,"start_character":2,"end_line":952,"end_character":15},"in_reply_to":"9abb7d3a_246bccf2","updated":"2016-05-31 18:16:09.000000000","message":"good point. But I don\u0027t like \"node_name\" very much....any ideas?","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"0432d243785bf5a30ce57a2bd05a1f9391436b3f","unresolved":false,"context_lines":[{"line_number":949,"context_line":"  project are immediately invalidated. Re-enabling a project does not re-enable"},{"line_number":950,"context_line":"  pre-existing tokens."},{"line_number":951,"context_line":""},{"line_number":952,"context_line":"- ``leaf_name`` (string) *New in version 3.7*"},{"line_number":953,"context_line":""},{"line_number":954,"context_line":"  Represents the name of the project node in the hierarchy, as opposed to the"},{"line_number":955,"context_line":"  ``name`` attribute that includes the path to the root project. ``leaf_name``"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_ca6927fb","line":952,"range":{"start_line":952,"start_character":2,"end_line":952,"end_character":15},"in_reply_to":"9abb7d3a_4a6c1735","updated":"2016-05-31 18:41:05.000000000","message":"\"relative_name\" (like relative path)","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"c3f975d2422c34f08fe0a17896cb1d8ad209e919","unresolved":false,"context_lines":[{"line_number":949,"context_line":"  project are immediately invalidated. Re-enabling a project does not re-enable"},{"line_number":950,"context_line":"  pre-existing tokens."},{"line_number":951,"context_line":""},{"line_number":952,"context_line":"- ``leaf_name`` (string) *New in version 3.7*"},{"line_number":953,"context_line":""},{"line_number":954,"context_line":"  Represents the name of the project node in the hierarchy, as opposed to the"},{"line_number":955,"context_line":"  ``name`` attribute that includes the path to the root project. ``leaf_name``"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_4a6c1735","line":952,"range":{"start_line":952,"start_character":2,"end_line":952,"end_character":15},"in_reply_to":"9abb7d3a_ef7a3df0","updated":"2016-05-31 18:36:24.000000000","message":"\"node_name\" sounds more appropriate though, let\u0027s see if others have a better idea :)","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"ab51907f10dfc8f1d820663e7af6f4f5e259a98f","unresolved":false,"context_lines":[{"line_number":2015,"context_line":"        }"},{"line_number":2016,"context_line":"    }"},{"line_number":2017,"context_line":""},{"line_number":2018,"context_line":"A project scoped token to a project acting as a domain will have the"},{"line_number":2019,"context_line":"``is_domain`` attribute set to true."},{"line_number":2020,"context_line":""},{"line_number":2021,"context_line":""},{"line_number":2022,"context_line":"Domain Scope"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9abb7d3a_c43760fd","line":2019,"range":{"start_line":2018,"start_character":0,"end_line":2019,"end_character":36},"updated":"2016-05-31 18:05:32.000000000","message":"where is that?","commit_id":"7075106a0b3a3c2e68ba43892015f94413731bc5"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"aa399113dd25b4da5e77ec19a1341e041b32dcfd","unresolved":false,"context_lines":[{"line_number":978,"context_line":"            \"links\": {"},{"line_number":979,"context_line":"                \"self\": \"http://identity:35357/v3/projects/263fd9\""},{"line_number":980,"context_line":"            },"},{"line_number":981,"context_line":"            \"name\": \"project-x\","},{"line_number":982,"context_line":"            \"parent_id\": \"1789d1\","},{"line_number":983,"context_line":"            \"is_domain\": false"},{"line_number":984,"context_line":"        }"}],"source_content_type":"text/x-rst","patch_set":8,"id":"7aa08908_fbcee681","side":"PARENT","line":981,"updated":"2016-06-06 15:30:55.000000000","message":"Isn\u0027t the name here suppose to reference the name of domain 1789d1?","commit_id":"9dbbbabaa94f29410fb5af0ba654eb02e9be2046"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"71332f8e85c6d0cdfe8d5708f33f6281da6a187f","unresolved":false,"context_lines":[{"line_number":2526,"context_line":"                \"name\": \"Test Group\""},{"line_number":2527,"context_line":"            },"},{"line_number":2528,"context_line":"            {"},{"line_number":2529,"context_line":"                \"domain_id\": \"1789d1\","},{"line_number":2530,"context_line":"                \"enabled\": true,"},{"line_number":2531,"context_line":"                \"id\": \"50ef01\","},{"line_number":2532,"context_line":"                \"links\": {"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9abb7d3a_42072d1d","side":"PARENT","line":2529,"updated":"2016-06-03 13:26:24.000000000","message":"Remove this \u0027Test\u0027","commit_id":"9dbbbabaa94f29410fb5af0ba654eb02e9be2046"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"aa399113dd25b4da5e77ec19a1341e041b32dcfd","unresolved":false,"context_lines":[{"line_number":1006,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":1007,"context_line":"            \"enabled\": true,"},{"line_number":1008,"context_line":"            \"id\": \"63abc1\","},{"line_number":1009,"context_line":"            \"name\": \"project-x/project-y\","},{"line_number":1010,"context_line":"            \"links\": {"},{"line_number":1011,"context_line":"                \"self\": \"http://identity:35357/v3/projects/63abc1\""},{"line_number":1012,"context_line":"            },"}],"source_content_type":"text/x-rst","patch_set":8,"id":"7aa08908_db920a57","line":1009,"updated":"2016-06-06 15:30:55.000000000","message":"How come domain names aren\u0027t included in the project name?","commit_id":"19736077438bb5a54d2fe5ef5b0f58d532916552"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"71332f8e85c6d0cdfe8d5708f33f6281da6a187f","unresolved":false,"context_lines":[{"line_number":2582,"context_line":"                \"name\": \"Test Group\""},{"line_number":2583,"context_line":"            },"},{"line_number":2584,"context_line":"            {"},{"line_number":2585,"context_line":"                \"domain_id\": \"1789d1\",Test"},{"line_number":2586,"context_line":"                \"enabled\": true,"},{"line_number":2587,"context_line":"                \"id\": \"50ef01\","},{"line_number":2588,"context_line":"                \"node_name\": \"Build Group\","}],"source_content_type":"text/x-rst","patch_set":8,"id":"9abb7d3a_a206d91d","line":2585,"updated":"2016-06-03 13:26:24.000000000","message":"remove this Test here","commit_id":"19736077438bb5a54d2fe5ef5b0f58d532916552"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"dbd643240d59b2426cf982feca0de81901ec9008","unresolved":false,"context_lines":[{"line_number":2582,"context_line":"                \"name\": \"Test Group\""},{"line_number":2583,"context_line":"            },"},{"line_number":2584,"context_line":"            {"},{"line_number":2585,"context_line":"                \"domain_id\": \"1789d1\",Test"},{"line_number":2586,"context_line":"                \"enabled\": true,"},{"line_number":2587,"context_line":"                \"id\": \"50ef01\","},{"line_number":2588,"context_line":"                \"node_name\": \"Build Group\","}],"source_content_type":"text/x-rst","patch_set":8,"id":"7aa08908_7b74b69b","line":2585,"in_reply_to":"9abb7d3a_a206d91d","updated":"2016-06-06 15:19:28.000000000","message":"Is this what\u0027s causing the build to be unstable?","commit_id":"19736077438bb5a54d2fe5ef5b0f58d532916552"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"c12740ea885e7bbd6ea0df9c4c9b2c02193eeced","unresolved":false,"context_lines":[{"line_number":4137,"context_line":"The key requirements when creating a project are to define the domain it will"},{"line_number":4138,"context_line":"owned by, it\u0027s name and where it sits in the project hierarchy."},{"line_number":4139,"context_line":""},{"line_number":4140,"context_line":"Starting with version 3.7, since the name contains the path relative to the"},{"line_number":4141,"context_line":"domain, a parent_id is not required, so an example request would be:"},{"line_number":4142,"context_line":""},{"line_number":4143,"context_line":"::"},{"line_number":4144,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_24e9bf7f","line":4141,"range":{"start_line":4140,"start_character":0,"end_line":4141,"end_character":68},"updated":"2016-06-14 18:36:20.000000000","message":"Some have suggested we shouldn\u0027t enhance create project in this way - since you can already provide a parent_id. The question is whether using name in a NON path way in the 3.7 API would be inconsistent with how we use it elsewhere....","commit_id":"ba5e39177b39db046d627b537f9d481132ac709f"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"917ed7afece5bac3e285afe7343ef37752dee939","unresolved":false,"context_lines":[{"line_number":902,"context_line":"  Unique project name, within the owning domain. A project name for a project"},{"line_number":903,"context_line":"  acting as a domain must be unique across all domains. Starting with version"},{"line_number":904,"context_line":"  3.7, the name includes the path to the root of any project hierarchy, not"},{"line_number":905,"context_line":"  including the project acting as a domain."},{"line_number":906,"context_line":""},{"line_number":907,"context_line":"Optional attributes:"},{"line_number":908,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"3aaa91ec_db719fe2","line":905,"updated":"2016-06-21 19:15:43.000000000","message":"How does this play with the reseller idea where they might not know the entire hierarchy?","commit_id":"eff6dc4f1405304b7572d365db7bb43c757e117e"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"2f0443c3cc75622c6a3444fd7a2f927b5cfd1319","unresolved":false,"context_lines":[{"line_number":902,"context_line":"  Unique project name, within the owning domain. A project name for a project"},{"line_number":903,"context_line":"  acting as a domain must be unique across all domains. Starting with version"},{"line_number":904,"context_line":"  3.7, the name includes the path to the root of any project hierarchy, not"},{"line_number":905,"context_line":"  including the project acting as a domain."},{"line_number":906,"context_line":""},{"line_number":907,"context_line":"Optional attributes:"},{"line_number":908,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"3aaa91ec_4c07861c","line":905,"in_reply_to":"3aaa91ec_db719fe2","updated":"2016-06-22 13:04:14.000000000","message":"in this proposal, anyway, the only need to path of projects up to the closest domain....if we do reseller, it will be above that","commit_id":"eff6dc4f1405304b7572d365db7bb43c757e117e"}],"specs/keystone/newton/hierarchical-project-naming.rst":[{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"fa4a91a05800a8a84ce663096591f40aaf8d04b5","unresolved":false,"context_lines":[{"line_number":21,"context_line":"hierarchy within that domain. As project hierarchies grow, this will become"},{"line_number":22,"context_line":"increasingly untenable."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"While a longer term goal may be to relex this constraint, this would affect"},{"line_number":25,"context_line":"many clients of keystone. An alternative, is therefore being proposed."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab6814e_6dbe99d5","line":24,"updated":"2016-05-19 13:53:03.000000000","message":"nit: relax","commit_id":"bfcce8ac205a3f522d7f5b3133f827cf019b7b82"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":34,"context_line":"could exist in the hierarchy:"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"name1 \u003d development/sas/myproject"},{"line_number":37,"context_line":"name2 \u003d development/internal/myproject"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":40,"context_line":"project paths in an API request, by supporting an optional ability"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_382484c3","line":37,"updated":"2016-05-31 21:31:26.000000000","message":"Make this a code block?","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":34,"context_line":"could exist in the hierarchy:"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"name1 \u003d development/sas/myproject"},{"line_number":37,"context_line":"name2 \u003d development/internal/myproject"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":40,"context_line":"project paths in an API request, by supporting an optional ability"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_69464050","line":37,"in_reply_to":"9abb7d3a_382484c3","updated":"2016-05-31 22:22:07.000000000","message":"Done","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":37,"context_line":"name2 \u003d development/internal/myproject"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":40,"context_line":"project paths in an API request, by supporting an optional ability"},{"line_number":41,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":42,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":43,"context_line":"separator that is one of the reserved characters defined in section 2.2"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_b81eb46d","line":40,"updated":"2016-05-31 21:31:26.000000000","message":"path*?","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":37,"context_line":"name2 \u003d development/internal/myproject"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":40,"context_line":"project paths in an API request, by supporting an optional ability"},{"line_number":41,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":42,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":43,"context_line":"separator that is one of the reserved characters defined in section 2.2"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_2940b833","line":40,"in_reply_to":"9abb7d3a_b81eb46d","updated":"2016-05-31 22:22:07.000000000","message":"Done","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":122,"context_line":"An intended side effect of this new auth capability is that it is now possible"},{"line_number":123,"context_line":"to get a project scoped token to a project acting as a domain (this is not"},{"line_number":124,"context_line":"possible in the current API). For example to get a project scoped token to the"},{"line_number":125,"context_line":"domain called development above, the following auth request could be used:"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"::"},{"line_number":128,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_53984bc0","line":125,"updated":"2016-05-31 21:31:26.000000000","message":"Isn\u0027t the domain above acme.com? /development looks like the first child-project of the acme.com domain.","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":122,"context_line":"An intended side effect of this new auth capability is that it is now possible"},{"line_number":123,"context_line":"to get a project scoped token to a project acting as a domain (this is not"},{"line_number":124,"context_line":"possible in the current API). For example to get a project scoped token to the"},{"line_number":125,"context_line":"domain called development above, the following auth request could be used:"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"::"},{"line_number":128,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_c975ac98","line":125,"in_reply_to":"9abb7d3a_53984bc0","updated":"2016-05-31 22:22:07.000000000","message":"oops, yes!","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Such a token would, as per the current specification for tokens, include the"},{"line_number":143,"context_line":"`is_domain` attribute set `true`, allowing for policy enforcement on domain"},{"line_number":144,"context_line":"operations using project scoped tokens, allowing for the eventual deprecation"},{"line_number":145,"context_line":"of domain tokens altogether."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"Alternatives"},{"line_number":148,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_133fe387","line":145,"updated":"2016-05-31 21:31:26.000000000","message":"Couldn\u0027t the authentication code path check for this and not allow it?","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Such a token would, as per the current specification for tokens, include the"},{"line_number":143,"context_line":"`is_domain` attribute set `true`, allowing for policy enforcement on domain"},{"line_number":144,"context_line":"operations using project scoped tokens, allowing for the eventual deprecation"},{"line_number":145,"context_line":"of domain tokens altogether."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"Alternatives"},{"line_number":148,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_e97070a6","line":145,"in_reply_to":"9abb7d3a_133fe387","updated":"2016-05-31 22:22:07.000000000","message":"not sure I follow your question...","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":155,"context_line":"On migration, the project names will be converted to full path names. To avoid"},{"line_number":156,"context_line":"a long migration time, this will be done on-the-fly as projects are accessed,"},{"line_number":157,"context_line":"rather than in one go at upgrade time. This on-the-fly migration will be"},{"line_number":158,"context_line":"hidden within the sql driver layer."},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"REST API Impact"},{"line_number":161,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_b36417b9","line":158,"updated":"2016-05-31 21:31:26.000000000","message":"An alternative could be to batch process project names using the keystone-manage command.","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":155,"context_line":"On migration, the project names will be converted to full path names. To avoid"},{"line_number":156,"context_line":"a long migration time, this will be done on-the-fly as projects are accessed,"},{"line_number":157,"context_line":"rather than in one go at upgrade time. This on-the-fly migration will be"},{"line_number":158,"context_line":"hidden within the sql driver layer."},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"REST API Impact"},{"line_number":161,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_296718ea","line":158,"in_reply_to":"9abb7d3a_b36417b9","updated":"2016-05-31 22:22:07.000000000","message":"Agreed.","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c95ad045c87e82ef4190aea1ff13ce0f4150f312","unresolved":false,"context_lines":[{"line_number":207,"context_line":"Dependencies"},{"line_number":208,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":209,"context_line":""},{"line_number":210,"context_line":"Microversion support in Keystone, see: https://review.openstack.org/#/c/315180/"},{"line_number":211,"context_line":""},{"line_number":212,"context_line":"Testing"},{"line_number":213,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_936ab37f","line":210,"updated":"2016-05-31 21:31:26.000000000","message":"Make this an RST link?","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"833fa861db9f396deb97d67bb8bb2735742dd506","unresolved":false,"context_lines":[{"line_number":207,"context_line":"Dependencies"},{"line_number":208,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":209,"context_line":""},{"line_number":210,"context_line":"Microversion support in Keystone, see: https://review.openstack.org/#/c/315180/"},{"line_number":211,"context_line":""},{"line_number":212,"context_line":"Testing"},{"line_number":213,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9abb7d3a_8960c4d0","line":210,"in_reply_to":"9abb7d3a_936ab37f","updated":"2016-05-31 22:22:07.000000000","message":"Done","commit_id":"0d922dc60d87c5dc7abd7b92187b8bc132e01f49"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":28,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"The proposal is to change the name of projects to be their full path, including"},{"line_number":31,"context_line":"the leaf name). In this way, this (full) name will remain unique, while"},{"line_number":32,"context_line":"allowing projects within the hierarchy to have duplicate names (as long as"},{"line_number":33,"context_line":"they have different parents). For example, two projects called \"myproject\""},{"line_number":34,"context_line":"could exist in the hierarchy:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_f2982f7a","line":31,"updated":"2016-06-01 15:19:34.000000000","message":"s/)//","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":28,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"The proposal is to change the name of projects to be their full path, including"},{"line_number":31,"context_line":"the leaf name). In this way, this (full) name will remain unique, while"},{"line_number":32,"context_line":"allowing projects within the hierarchy to have duplicate names (as long as"},{"line_number":33,"context_line":"they have different parents). For example, two projects called \"myproject\""},{"line_number":34,"context_line":"could exist in the hierarchy:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_4bf4e659","line":31,"in_reply_to":"9abb7d3a_f2982f7a","updated":"2016-06-01 15:55:59.000000000","message":"Done","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":41,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":42,"context_line":"project path in an API request, by supporting an optional ability"},{"line_number":43,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":44,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":45,"context_line":"separator that is one of the reserved characters defined in section 2.2"},{"line_number":46,"context_line":"of rfc3986 \u003chttp://tools.ietf.org/html/rfc3986\u003e_) to address a"},{"line_number":47,"context_line":"project, if we were to provide one. For example:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_12a85376","line":44,"updated":"2016-06-01 15:19:34.000000000","message":"nit: use a hierarchical naming scheme *","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":41,"context_line":"In Mitaka, we laid the ground work for allowing the specification of a"},{"line_number":42,"context_line":"project path in an API request, by supporting an optional ability"},{"line_number":43,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":44,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":45,"context_line":"separator that is one of the reserved characters defined in section 2.2"},{"line_number":46,"context_line":"of rfc3986 \u003chttp://tools.ietf.org/html/rfc3986\u003e_) to address a"},{"line_number":47,"context_line":"project, if we were to provide one. For example:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_eb703a0d","line":44,"in_reply_to":"9abb7d3a_12a85376","updated":"2016-06-01 15:55:59.000000000","message":"Done","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":43,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":44,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":45,"context_line":"separator that is one of the reserved characters defined in section 2.2"},{"line_number":46,"context_line":"of rfc3986 \u003chttp://tools.ietf.org/html/rfc3986\u003e_) to address a"},{"line_number":47,"context_line":"project, if we were to provide one. For example:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_52bc9bba","line":46,"updated":"2016-06-01 15:19:34.000000000","message":"nit: s/address/reference/","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":43,"context_line":"to make sure project names are url safe [1]. Deployments that are running with"},{"line_number":44,"context_line":"this feature enabled could reliably use hierarchical naming scheme (with a"},{"line_number":45,"context_line":"separator that is one of the reserved characters defined in section 2.2"},{"line_number":46,"context_line":"of rfc3986 \u003chttp://tools.ietf.org/html/rfc3986\u003e_) to address a"},{"line_number":47,"context_line":"project, if we were to provide one. For example:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_6b63aa42","line":46,"in_reply_to":"9abb7d3a_52bc9bba","updated":"2016-06-01 15:55:59.000000000","message":"Done","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":63,"context_line":"            }"},{"line_number":64,"context_line":"        }"},{"line_number":65,"context_line":"    }"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"It is proposed that we now enable this capability, and at the same time switch"},{"line_number":68,"context_line":"to full path naming for all project names. Since this change is potentially"},{"line_number":69,"context_line":"backwardly incompatible, this will be tied to a microversion of the keystone"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_124973b7","line":66,"updated":"2016-06-01 15:19:34.000000000","message":"This is probably more of an implementation detail - but we currently only allow project names to be 64 characters long [0]. This would for sure require a database migration to change the data type of the resource.project.name column. What do we set that to and what is the absolute limit of hierarchical project name length? \n\n\n[0] https://github.com/openstack/keystone/blob/c90c525aacfb8a46677673d735a1dfec3f9e9c20/keystone/resource/schema.py#L27","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":63,"context_line":"            }"},{"line_number":64,"context_line":"        }"},{"line_number":65,"context_line":"    }"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"It is proposed that we now enable this capability, and at the same time switch"},{"line_number":68,"context_line":"to full path naming for all project names. Since this change is potentially"},{"line_number":69,"context_line":"backwardly incompatible, this will be tied to a microversion of the keystone"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_8bd36ed4","line":66,"in_reply_to":"9abb7d3a_124973b7","updated":"2016-06-01 15:55:59.000000000","message":"yrs, I need to add info about that.....","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":102,"context_line":"- GET /auth/projects"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"So as to not require the full path name of a project on, for example, create"},{"line_number":105,"context_line":"project (since you can already supply a parent_id), a new attribute called"},{"line_number":106,"context_line":"leaf_name will be added to the project entity (which essentially holds what"},{"line_number":107,"context_line":"was previously stored in the project name). The use of this new attribute is"},{"line_number":108,"context_line":"optional, and need only be used if the caller does not want to manipulate the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_d2752bcb","line":105,"updated":"2016-06-01 15:19:34.000000000","message":"Adding the ability to create a project with a full path name, a leaf name, and a parent_id seems like a lot of ways to do the same thing.\n\nDoing: \n\n    create project /acme.com/development/sas/myproject\n\nAssumes that I have the create_project capability on the parent sas project. I think we can get all the information versus something like: \n\n    create project --leaf-name myproject --domain-id acme.com --parent-id sas\n\nWith the current API, parent_project_id isn\u0027t required is it? Would performing project create this way now require parent_project_id on every create project request? Also, does returning the full path as the project name hinder the ability to accomplish the reseller case in the future?","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":102,"context_line":"- GET /auth/projects"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"So as to not require the full path name of a project on, for example, create"},{"line_number":105,"context_line":"project (since you can already supply a parent_id), a new attribute called"},{"line_number":106,"context_line":"leaf_name will be added to the project entity (which essentially holds what"},{"line_number":107,"context_line":"was previously stored in the project name). The use of this new attribute is"},{"line_number":108,"context_line":"optional, and need only be used if the caller does not want to manipulate the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_0b677eb7","line":105,"in_reply_to":"9abb7d3a_d2752bcb","updated":"2016-06-01 15:55:59.000000000","message":"So we do support (today) the ability to supply name + parent_id in order to place a project at the required place in the hierarchy. Note that if you specify  parent_id, you don\u0027t also need domain_id (since this is implied by the parent). parene_id is optional, but if not used (today) the project will be a top level project (since you only have name + domain_id). \n\nSo I agree that there now seems multiple ways of doing this....but if (as per this spec) we return names as paths, it seems we should allow you to specify a path on created. What I don\u0027t like about the path idea, is that looking at a project entity (say from a GET /project), you have domain_id, parent_id and a full path....which seems to duplicate information.","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ca525b322080ca46453d8f39362b99c2aaf39e3a","unresolved":false,"context_lines":[{"line_number":124,"context_line":"An intended side effect of this new auth capability is that it is now possible"},{"line_number":125,"context_line":"to get a project scoped token to a project acting as a domain (this is not"},{"line_number":126,"context_line":"possible in the current API). For example to get a project scoped token to the"},{"line_number":127,"context_line":"domain called acme.com above, the following auth request could be used:"},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"::"},{"line_number":130,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_52c01b50","line":127,"updated":"2016-06-01 15:19:34.000000000","message":"Could logic be added to the current authentication flow that dis-allows getting a domain-scoped token? Maybe a prerequisite to this spec would be to deprecate and remove the ability to get a domain-scoped token?","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"56a23ccd7cd34482144cbe93e5104e98e770074f","unresolved":false,"context_lines":[{"line_number":124,"context_line":"An intended side effect of this new auth capability is that it is now possible"},{"line_number":125,"context_line":"to get a project scoped token to a project acting as a domain (this is not"},{"line_number":126,"context_line":"possible in the current API). For example to get a project scoped token to the"},{"line_number":127,"context_line":"domain called acme.com above, the following auth request could be used:"},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"::"},{"line_number":130,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"9abb7d3a_2b2082f6","line":127,"in_reply_to":"9abb7d3a_52c01b50","updated":"2016-06-01 15:55:59.000000000","message":"I think the agreement was that we would still support domain scoped tokens  I.e. by specify an explicit domain scope in the auth request) for a while. In the meantime, I don\u0027t think we should avoid getting a project scoped token to a project acting as a domain...but of course a policy file could chose to not allow project actions if the \"is_domain\" flag is set in the token","commit_id":"af77a1478501e38ef8f1520450c52ca9aa2f984a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"aa399113dd25b4da5e77ec19a1341e041b32dcfd","unresolved":false,"context_lines":[{"line_number":31,"context_line":"the node name. In this way, this (full) name will remain unique, while"},{"line_number":32,"context_line":"allowing projects within the hierarchy to have duplicate names (as long as"},{"line_number":33,"context_line":"they have different parents). For example, two projects called \"myproject\""},{"line_number":34,"context_line":"could exist in the hierarchy:"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":".. code-block:: python"},{"line_number":37,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"7aa08908_dbffaa32","line":34,"updated":"2016-06-06 15:30:55.000000000","message":"How come the domain name isn\u0027t included in project name?","commit_id":"19736077438bb5a54d2fe5ef5b0f58d532916552"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"6b32205cfe25707a673e6c380e4705cc7e5ca232","unresolved":false,"context_lines":[{"line_number":87,"context_line":"            },"},{"line_number":88,"context_line":"            \"scope\": {"},{"line_number":89,"context_line":"                \"project\": {"},{"line_number":90,"context_line":"                    \"name\": \"/acme.com/development/sas/myproject\""},{"line_number":91,"context_line":"                }"},{"line_number":92,"context_line":"            }"},{"line_number":93,"context_line":"        }"}],"source_content_type":"text/x-rst","patch_set":8,"id":"7aa08908_82c1d156","line":90,"range":{"start_line":90,"start_character":29,"end_line":90,"end_character":65},"updated":"2016-06-08 00:13:24.000000000","message":"Not sure if there\u0027s a UX concern here, but I can\u0027t imaging having to manually type in all this from CLI.","commit_id":"19736077438bb5a54d2fe5ef5b0f58d532916552"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"01a6293d24deab89bcde47de826e06f1b7fd650b","unresolved":false,"context_lines":[{"line_number":65,"context_line":"    }"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"It is proposed that we now enable this capability, and at the same time switch"},{"line_number":68,"context_line":"to full path naming for all project names. Since this change is potentially"},{"line_number":69,"context_line":"backwardly incompatible, this will be tied to a microversion of the keystone"},{"line_number":70,"context_line":"API. A 3.7 server will also default \u0027url_safe\u0027 to \u0027strict\u0027 mode. We will mark"},{"line_number":71,"context_line":"this config option as deprecated, so that we can remove the ability to turn"}],"source_content_type":"text/x-rst","patch_set":12,"id":"3aaa91ec_1b096732","line":68,"updated":"2016-06-21 18:14:24.000000000","message":"This change is not \"potentially backwards incompatible,\" this change is simply \"backwards incompatible.\"","commit_id":"eff6dc4f1405304b7572d365db7bb43c757e117e"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"01a6293d24deab89bcde47de826e06f1b7fd650b","unresolved":false,"context_lines":[{"line_number":121,"context_line":"a configuration option - however the confusion of having to know the"},{"line_number":122,"context_line":"separator for a given cloud (before you authenticate), seems to create a worse"},{"line_number":123,"context_line":"problem than simply having a fixed separator in the first place, so it is"},{"line_number":124,"context_line":"proposed that we do not allow the separator to be modified."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"An intended side effect of this new auth capability is that it is now possible"},{"line_number":127,"context_line":"to get a project scoped token to a project acting as a domain (this is not"}],"source_content_type":"text/x-rst","patch_set":12,"id":"3aaa91ec_266fea93","line":124,"updated":"2016-06-21 18:14:24.000000000","message":"++","commit_id":"eff6dc4f1405304b7572d365db7bb43c757e117e"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"01a6293d24deab89bcde47de826e06f1b7fd650b","unresolved":false,"context_lines":[{"line_number":173,"context_line":"  technically, we could try to maintain the ability to access projects created"},{"line_number":174,"context_line":"  before the server upgrade via their non-path name, it would get very"},{"line_number":175,"context_line":"  confusing for users having to remember which projects you could or couldn\u0027t"},{"line_number":176,"context_line":"  access this way."},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"Alternatives"},{"line_number":179,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"3aaa91ec_a13bc49b","line":176,"updated":"2016-06-21 18:14:24.000000000","message":"It\u0027s also confusing to change the way clients refer to project names in the first place.","commit_id":"eff6dc4f1405304b7572d365db7bb43c757e117e"}]}