Skip to content
This repository has been archived by the owner on Dec 7, 2020. It is now read-only.

url tokenization #80

Closed
gambol99 opened this issue May 14, 2016 · 2 comments
Closed

url tokenization #80

gambol99 opened this issue May 14, 2016 · 2 comments
Assignees

Comments

@gambol99
Copy link
Contributor

Would be nice to permit tokenizing the url for role extraction .. i.e. instead of using

--resource='uri:/logs/project1|roles=project1'
--resource='uri:/logs/project2|roles=project2'

Its preferable to use

--resource='uri:/logs/%role%'
@gambol99 gambol99 self-assigned this May 14, 2016
@gambol99 gambol99 added this to the v1.1.0 Release milestone May 14, 2016
@rvion
Copy link
Contributor

rvion commented May 14, 2016

thinking about it, this notation could also make sense

--resource='uri:/logs/%role%|roles=test1,test2

it would further restrict the list of roles allowed.

@rvion
Copy link
Contributor

rvion commented May 14, 2016

in order to unify this enhancement with [proposal https://github.com//issues/81], I would like to suggest using %roles%instead of %role% as url template.

  • simpler documentation
  • richer meaning

concrete example:

when we have

--resource='uri:/logs/%roles%|roles=test1+test2*(test3+test4)

%roles% would be the first valid set of roles according to the description:

uri:/logs/test1
uri:/logs/test2*test3
uri:/logs/test2*test4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants