refactor: reorg sessions strings
This commit is contained in:
5 files changed
+15
-12
No files matched your search
@@ -1,6 +1,6 @@
|
||||
<Rose::Nav::Sidebar @title={{t "titles.resources"}} as |nav|>
|
||||
<nav.link @route="scopes.scope.projects.project.sessions">
|
||||
{{t "resources.sessions"}}
|
||||
{{t "resources.session.title_plural"}}
|
||||
</nav.link>
|
||||
<nav.link @route="scopes.scope.projects.project.targets">
|
||||
{{t "resources.targets"}}
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{{title (t "resources.sessions")}}
|
||||
{{title (t "resources.session.title_plural")}}
|
||||
|
||||
{{outlet}}
|
||||
@@ -5,7 +5,8 @@
|
||||
</page.breadcrumbs>
|
||||
|
||||
<page.header>
|
||||
<h2>{{t "resources.sessions"}}</h2>
|
||||
<h2>{{t "resources.session.title_plural"}}</h2>
|
||||
<p>{{t "resources.session.description"}}</p>
|
||||
</page.header>
|
||||
|
||||
<page.body>
|
||||
@@ -52,9 +53,9 @@
|
||||
{{else}}
|
||||
|
||||
<Rose::Layout::Centered>
|
||||
<Rose::Message @title={{t "titles.no-sessions"}} as |message|>
|
||||
<Rose::Message @title={{t "resources.session.messages.none.title"}} as |message|>
|
||||
<message.description>
|
||||
{{t "descriptions.no-sessions"}}
|
||||
{{t "resources.session.messages.none.description"}}
|
||||
</message.description>
|
||||
</Rose::Message>
|
||||
</Rose::Layout::Centered>
|
||||
|
||||
@@ -47,7 +47,6 @@ titles:
|
||||
members: Members
|
||||
group-members-welcome: Welcome to Members
|
||||
no-available-users: No Users Available
|
||||
no-sessions: No Active Sessions
|
||||
actions: Actions
|
||||
descriptions:
|
||||
host-catalogs: Overview of collections of hosts and host sets.
|
||||
@@ -68,4 +67,3 @@ descriptions:
|
||||
no-principals-available: Principals are not available for assignment.
|
||||
group-members-welcome: Users belonging to this group appear here.
|
||||
no-available-users: No users are available to add to this group.
|
||||
no-sessions: There are no active sessions at this time.
|
||||
@@ -23,12 +23,20 @@ auth-method:
|
||||
description: Auth methods are configurations to authenticate users.
|
||||
none:
|
||||
title: No Authentication Methods
|
||||
description: No authentication methods were found for this scope. Switch scopes and try again.
|
||||
description: No authentication methods were found for this scope.
|
||||
types:
|
||||
password: Password
|
||||
actions:
|
||||
create: Create Auth Method
|
||||
delete: Delete Auth Method
|
||||
session:
|
||||
title: Session
|
||||
title_plural: Sessions
|
||||
description: A session is a connection to a target initiated through Boundary.
|
||||
messages:
|
||||
none:
|
||||
title: No Sessions
|
||||
description: There are no active sessions within the current scope.
|
||||
user: User
|
||||
users: Users
|
||||
role: Role
|
||||
@@ -47,8 +55,6 @@ host: Host
|
||||
hosts: Hosts
|
||||
target: Target
|
||||
targets: Targets
|
||||
sessions: Sessions
|
||||
session: Session
|
||||
descriptions:
|
||||
user: A User inherits from Principal ("is-a" Principal) allowing it to be associated with zero or more Roles.
|
||||
users: A user is any entity authorized to access Boundary using authentication credentials specific to one of the configured Authentication Methods. A User is owned by one and only one Organization. A User is associated with zero or one Authentication Methods. A User not associated with an Authentication Method can not log in to the system. A User can belong to zero or more Groups. A User is deleted when the Organization it belongs to is deleted. The lifecycle of a User is not tied to the lifecycle of any Authentication Method, Group or Role, but rather to its Organization only.
|
||||
@@ -70,5 +76,3 @@ descriptions:
|
||||
hosts: A host is a computing element with a network address reachable from Boundary. A Host belongs to one and only one Host Catalog. A Host can be contained by zero or more Host Sets. The lifecycle of a Host is not tied to the lifecycle of any Host Sets.
|
||||
target: Target is abstract. A Target is deleted when the Scope it belongs to is deleted.
|
||||
targets: A target is a networked service a User can connect to and interact with through Boundary. A Target does not directly contain any secrets. A Target contains a collection of Hosts. A Target belongs to one and only one Scope. A Target can contain zero or more Host Sets. The lifecycle of a Target is not tied to the lifecycle of any Host Set.
|
||||
sessions: Sessions
|
||||
session: Session
|
||||
Reference in new issue
Block a user