You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/eportal/README.md
+44-30Lines changed: 44 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -821,6 +821,50 @@ A new table is added to the starting page. This table displays the following:
821
821
822
822
The number of servers for each key is listed on the _Keys_ page.
823
823
824
+
## Managing server tags
825
+
826
+
You can use 'Server tags' page to deal with tags.
827
+
828
+

829
+
830
+
Tagging is a convenient way to group servers by any criteria. For example OS, deployment environment, location, etc.
831
+
You need to create a tag and then it can be assigned to a server from the [Managing Servers](#managing-servers) interface.
832
+
833
+

834
+
835
+
The tag may have an optional value. For example, this allows you to introduce a new geo location without creating a new tag for it.
836
+
837
+
### Using agent CLI to manage tags
838
+
839
+
To add an extra Tag field for the server, run:
840
+
841
+
```text
842
+
# kcarectl --tag command
843
+
```
844
+
845
+
where `command` is a parameter defined by a user. This parameter will be displayed in UI for the server. User could add multiple tags for each server. Each tag should be separated with `;` symbol.
846
+
847
+
Example:
848
+
849
+
```text
850
+
# kcarectl --tag "env:prod;ubuntu"
851
+
```
852
+
853
+
This server has two tags : `env:prod` and `ubuntu`.
854
+
855
+
`env:prod` is a parameter that has tag name `env` and the value `prod`.
856
+
857
+

858
+
859
+
To remove all tags from a particular server, run:
860
+
861
+
```text
862
+
# kcarectl --tag ""
863
+
```
864
+
865
+
Where `""` is a parameter to delete the previously defined tag.
866
+
867
+
824
868
## Feed Management
825
869
826
870
Feeds are intended to manage patchsets on the server, and they provide a possibility to bind a set of patches to a specific key. Possible use cases:
@@ -946,36 +990,6 @@ The API key is personal, meaning it is tied to a specific user and inherits thei
946
990
A user with read-only permissions can only manage their own keys,
947
991
while an administrator has access to any user's API keys.
948
992
949
-
## Adding extra Tag field
950
-
951
-
To add an extra Tag field for the server, run:
952
-
953
-
```text
954
-
# kcarectl --tag command
955
-
```
956
-
957
-
where `command` is a parameter defined by a user. This parameter will be displayed in UI for the server. User could add multiple tags for each server. Each tag should be separated with `;` symbol.
958
-
959
-
Example:
960
-
961
-
```text
962
-
# kcarectl --tag "env:prod;ubuntu"
963
-
```
964
-
965
-
This server has two tags : `env:prod` and `ubuntu`.
966
-
967
-
`env:prod` is a parameter that has tag name `env` and the value `prod`.
968
-
969
-

970
-
971
-
To remove all tags from a particular server, run:
972
-
973
-
```text
974
-
# kcarectl --tag ""
975
-
```
976
-
977
-
Where `""` is a parameter to delete the previously defined tag.
978
-
979
993
## How to setup ePortal to use HTTPS
980
994
981
995
Some assumptions for a server where e-portal is deployed:
0 commit comments