2018-10-19 15:17:02 +00:00
|
|
|
{{#app-view class=(concat 'policy ' (if (not isAuthorized) 'edit' 'list')) loading=isLoading authorized=isAuthorized enabled=isEnabled}}
|
2020-01-22 12:08:29 +00:00
|
|
|
{{#block-slot name='notification' as |status type|}}
|
|
|
|
|
{{partial 'dc/acls/policies/notifications'}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='header'}}
|
|
|
|
|
<h1>
|
|
|
|
|
Access Controls
|
|
|
|
|
</h1>
|
|
|
|
|
{{#if isAuthorized }}
|
|
|
|
|
{{partial 'dc/acls/nav'}}
|
|
|
|
|
{{/if}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='disabled'}}
|
|
|
|
|
{{partial 'dc/acls/disabled'}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='authorization'}}
|
|
|
|
|
{{partial 'dc/acls/authorization'}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='actions'}}
|
|
|
|
|
<a data-test-create href="{{href-to 'dc.acls.policies.create'}}" class="type-create">Create</a>
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='content'}}
|
2018-10-19 15:17:02 +00:00
|
|
|
{{#if (gt items.length 0) }}
|
2020-01-22 12:08:29 +00:00
|
|
|
<form class="filter-bar">
|
|
|
|
|
{{freetext-filter searchable=searchable value=s placeholder="Search"}}
|
|
|
|
|
</form>
|
2018-10-19 15:17:02 +00:00
|
|
|
{{/if}}
|
2020-01-22 12:08:29 +00:00
|
|
|
{{#changeable-set dispatcher=searchable}}
|
|
|
|
|
{{#block-slot name='set' as |filtered|}}
|
|
|
|
|
{{#tabular-collection
|
|
|
|
|
items=(sort-by 'CreateIndex:desc' 'Name:asc' filtered) as |item index|
|
|
|
|
|
}}
|
|
|
|
|
{{#block-slot name='header'}}
|
|
|
|
|
<th>Name</th>
|
|
|
|
|
<th>Datacenters</th>
|
|
|
|
|
<th>Description</th>
|
ui: Async Search (#4859)
This does several things to make improving the search experience easier
moving forwards:
1. Separate searching off from filtering. 'Searching' can be thought of
as specifically 'text searching' whilst filtering is more of a
boolean/flag search.
2. Decouple the actual searching functionality to almost pure,
isolated / unit testable units and unit test. (I still import embers get
which, once I upgrade to 3.5, I shouldn't need)
3. Searching rules are now configurable from the outside, i.e. not
wrapped in Controllers or Components.
4. General searching itself now can use an asynchronous approach based on
events. This prepares for future possibilities of handing off the
searching to a web worker or elsewhere, which should aid in large scale
searching and prepares the way for other searching methods.
5. Adds the possibility of have multiple searches in one
template/route/page.
Additionally, this adds a WithSearching mixin to aid linking the
searching to ember in an ember-like way in a single place. Plus a
WithListeners mixin to aid with cleaning up of event listeners on
Controller/Component destruction.
Post-initial work I slightly changed the API of create listeners:
Returning the handler from a `remover` means you can re-add it again if you
want to, this avoids having to save a reference to the handler elsewhere
to do the same.
The `remove` method itself now returns an array of handlers, again you
might want to use these again or something, and its also more useful
then just returning an empty array.
The more I look at this the more I doubt that you'll ever use `remove`
to remove individual handlers, you may aswell just use the `remover`
returned from add. I've added some comments to reflect this, but they'll
likely be removed once I'm absolutely sure of this.
I also added some comments for WithSearching to explain possible further
work re: moving `searchParams` so it can be `hung` off the
controller object
2018-11-06 09:10:20 +00:00
|
|
|
{{/block-slot}}
|
2020-01-22 12:08:29 +00:00
|
|
|
{{#block-slot name='row'}}
|
|
|
|
|
<td data-test-policy="{{item.Name}}">
|
|
|
|
|
<a href={{href-to 'dc.acls.policies.edit' item.ID}} class={{if (eq (policy/typeof item) 'policy-management') 'is-management'}}>{{item.Name}}</a>
|
|
|
|
|
</td>
|
|
|
|
|
<td>
|
|
|
|
|
{{join ', ' (policy/datacenters item)}}
|
|
|
|
|
</td>
|
|
|
|
|
<td data-test-description>
|
|
|
|
|
<p>{{item.Description}}</p>
|
|
|
|
|
</td>
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='actions' as |index change checked|}}
|
|
|
|
|
{{#popover-menu expanded=(if (eq checked index) true false) onchange=(action change index) keyboardAccess=false}}
|
|
|
|
|
{{#block-slot name='trigger'}}
|
|
|
|
|
More
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='menu' as |confirm send keypressClick|}}
|
|
|
|
|
{{#if (eq (policy/typeof item) 'policy-management')}}
|
|
|
|
|
<li role="none">
|
|
|
|
|
<a role="menuitem" tabindex="-1" data-test-edit href={{href-to 'dc.acls.policies.edit' item.ID}}>View</a>
|
|
|
|
|
</li>
|
|
|
|
|
{{else}}
|
|
|
|
|
|
|
|
|
|
<li role="none">
|
|
|
|
|
<a role="menuitem" tabindex="-1" data-test-edit href={{href-to 'dc.acls.policies.edit' item.ID}}>Edit</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li role="none" class="dangerous">
|
|
|
|
|
<label for={{confirm}} role="menuitem" tabindex="-1" onkeypress={{keypressClick}} data-test-delete>Delete</label>
|
|
|
|
|
<div role="menu">
|
|
|
|
|
<div class="confirmation-alert warning">
|
|
|
|
|
<div>
|
|
|
|
|
<header>
|
|
|
|
|
Confirm Delete
|
|
|
|
|
</header>
|
|
|
|
|
<p>
|
|
|
|
|
Are you sure you want to delete this policy?
|
|
|
|
|
</p>
|
|
|
|
|
</div>
|
|
|
|
|
<ul>
|
|
|
|
|
<li class="dangerous">
|
|
|
|
|
<button tabindex="-1" type="button" class="type-delete" onclick={{action send 'delete' item}}>Delete</button>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<label for={{confirm}}>Cancel</label>
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</li>
|
|
|
|
|
{{/if}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{/popover-menu}}
|
ui: Async Search (#4859)
This does several things to make improving the search experience easier
moving forwards:
1. Separate searching off from filtering. 'Searching' can be thought of
as specifically 'text searching' whilst filtering is more of a
boolean/flag search.
2. Decouple the actual searching functionality to almost pure,
isolated / unit testable units and unit test. (I still import embers get
which, once I upgrade to 3.5, I shouldn't need)
3. Searching rules are now configurable from the outside, i.e. not
wrapped in Controllers or Components.
4. General searching itself now can use an asynchronous approach based on
events. This prepares for future possibilities of handing off the
searching to a web worker or elsewhere, which should aid in large scale
searching and prepares the way for other searching methods.
5. Adds the possibility of have multiple searches in one
template/route/page.
Additionally, this adds a WithSearching mixin to aid linking the
searching to ember in an ember-like way in a single place. Plus a
WithListeners mixin to aid with cleaning up of event listeners on
Controller/Component destruction.
Post-initial work I slightly changed the API of create listeners:
Returning the handler from a `remover` means you can re-add it again if you
want to, this avoids having to save a reference to the handler elsewhere
to do the same.
The `remove` method itself now returns an array of handlers, again you
might want to use these again or something, and its also more useful
then just returning an empty array.
The more I look at this the more I doubt that you'll ever use `remove`
to remove individual handlers, you may aswell just use the `remover`
returned from add. I've added some comments to reflect this, but they'll
likely be removed once I'm absolutely sure of this.
I also added some comments for WithSearching to explain possible further
work re: moving `searchParams` so it can be `hung` off the
controller object
2018-11-06 09:10:20 +00:00
|
|
|
{{/block-slot}}
|
2020-01-22 12:08:29 +00:00
|
|
|
{{/tabular-collection}}
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{#block-slot name='empty'}}
|
|
|
|
|
<p>
|
|
|
|
|
There are no Policies.
|
|
|
|
|
</p>
|
|
|
|
|
{{/block-slot}}
|
|
|
|
|
{{/changeable-set}}
|
|
|
|
|
{{/block-slot}}
|
2018-10-19 15:17:02 +00:00
|
|
|
{{/app-view}}
|