mirror of
https://github.com/status-im/consul.git
synced 2025-01-24 04:31:12 +00:00
ee0e8bf500
This commit moves our in-app LockSessions code into an external 'app', which can theoretically be side-loaded but for now it just makes for good isolation/code hygiene. Functionally, there is kind of one change here, and that is we only show the 'Lock Session' tab if you have permissions to see them. Currently as our UI authorization endpoint needs to be changed slightly to suit our usecase, you will always have permissions to see Lock Sessions as we hardcode the session:read to true (obvs this is a frontend thing, not a backend thing), so it doesn't really change anything from a user perspective. Also added very bare docs while I was here. Small note here, ideally we need to add the each individual tab depending on whether an 'app' is enabled or not instead of just permissions, ideally it would be done totally from The Outside rather than a can based conditional on the inside, just something else to be thinking about for the future.
116 lines
3.3 KiB
Handlebars
116 lines
3.3 KiB
Handlebars
<Route
|
|
@name={{routeName}}
|
|
as |route|>
|
|
<DataLoader @src={{uri '/${partition}/${nspace}/${dc}/sessions/for-node/${node}'
|
|
(hash
|
|
partition=route.params.partition
|
|
nspace=route.params.nspace
|
|
dc=route.params.dc
|
|
node=route.params.name
|
|
)
|
|
}} as |api|>
|
|
|
|
<BlockSlot @name="error">
|
|
<AppError
|
|
@error={{api.error}}
|
|
@login={{route.model.app.login.open}}
|
|
/>
|
|
</BlockSlot>
|
|
|
|
<BlockSlot @name="loaded">
|
|
{{#let api.data as |items|}}
|
|
<div class="tab-section">
|
|
<DataWriter
|
|
@sink={{uri '/${partition}/${dc}/${nspace}/session/'
|
|
(hash
|
|
partition=route.params.partition
|
|
nspace=route.params.nspace
|
|
dc=route.params.dc
|
|
)
|
|
}}
|
|
@type="session"
|
|
@label="Lock Session"
|
|
@ondelete={{refresh-route}}
|
|
as |writer|>
|
|
|
|
<BlockSlot @name="removed" as |after|>
|
|
<Consul::LockSession::Notifications
|
|
{{notification
|
|
after=(action after)
|
|
}}
|
|
@type="remove"
|
|
/>
|
|
</BlockSlot>
|
|
|
|
<BlockSlot @name="error" as |after error|>
|
|
<Consul::LockSession::Notifications
|
|
{{notification
|
|
after=(action after)
|
|
}}
|
|
@type="remove"
|
|
@error={{error}}
|
|
/>
|
|
</BlockSlot>
|
|
|
|
<BlockSlot @name="content">
|
|
|
|
<DataCollection
|
|
@type="session"
|
|
@items={{items}}
|
|
as |collection|>
|
|
|
|
<collection.Collection>
|
|
<Consul::LockSession::List
|
|
@items={{collection.items}}
|
|
@ondelete={{writer.delete}}
|
|
/>
|
|
</collection.Collection>
|
|
|
|
<collection.Empty>
|
|
<EmptyState
|
|
@login={{route.model.app.login.open}}
|
|
>
|
|
<BlockSlot @name="header">
|
|
<h2>
|
|
Welcome to Lock Sessions
|
|
</h2>
|
|
</BlockSlot>
|
|
|
|
<BlockSlot @name="body">
|
|
<p>
|
|
Consul provides a session mechanism which can be used to build distributed locks. Sessions act as a binding layer between nodes, health checks, and key/value data. There are currently no lock sessions present, or you may not have permission to view lock sessions.
|
|
</p>
|
|
</BlockSlot>
|
|
|
|
<BlockSlot @name="actions">
|
|
<li class="docs-link">
|
|
<Action
|
|
@href="{{env 'CONSUL_DOCS_URL'}}/internals/sessions.html"
|
|
@external={{true}}
|
|
>
|
|
Documentation on Lock Sessions
|
|
</Action>
|
|
</li>
|
|
<li class="learn-link">
|
|
<Action
|
|
@href="{{env 'CONSUL_DOCS_LEARN_URL'}}/tutorials/consul/distributed-semaphore"
|
|
@external={{true}}
|
|
>
|
|
Read the guide
|
|
</Action>
|
|
</li>
|
|
</BlockSlot>
|
|
|
|
</EmptyState>
|
|
</collection.Empty>
|
|
|
|
</DataCollection>
|
|
|
|
</BlockSlot>
|
|
</DataWriter>
|
|
</div>
|
|
{{/let}}
|
|
</BlockSlot>
|
|
</DataLoader>
|
|
</Route>
|