Introduce tea organizations area command #263

Closed
opened 2020-12-05 19:28:06 +00:00 by khmarbaise · 6 comments
Member

I'm suggesting this cause I realized that the command

tea organizations ls

does not (yet) exist as well commands accordingly for the creation of organizations etc.

The question is: Is tea intended to make full administation/setup of Gitea possible in the future?

I've started to play around a little bit for that: a984d0e515

I'm suggesting this cause I realized that the command ``` tea organizations ls ``` does not (yet) exist as well commands accordingly for the creation of organizations etc. The question is: Is `tea` intended to make full administation/setup of Gitea possible in the future? I've started to play around a little bit for that: https://gitea.com/khmarbaise/tea/commit/a984d0e5158f57f1fac34fb4bc0fbc5d859a31ba

The question is: Is tea intended to make full administation/setup of Gitea possible in the future?

Yup, there should be another issue for admin commands even, to at least ls users on site, and create/update them w/ admin permissions.

> The question is: Is tea intended to make full administation/setup of Gitea possible in the future? Yup, there should be another issue for admin commands even, to at least `ls` users on site, and create/update them w/ admin permissions.
Author
Member

@techknowlogick Great to hear that. Related to #161

Second: Is the direction to create a set of sub commands to organizations like I suggested the right direction:

tea organizations list
tea organizations create
tea organizations delete

Or should that being done different? Meaning only via admin instead? But If I correctly understood the permission concept a user can also generate an organization?

@techknowlogick Great to hear that. Related to #161 Second: Is the direction to create a set of sub commands to `organizations` like I suggested the right direction: ``` tea organizations list tea organizations create tea organizations delete ``` Or should that being done different? Meaning only via `admin` instead? But If I correctly understood the permission concept a user can also generate an organization?
Author
Member

So based on my experiments the output of tea orgs ls could like this: (Yes much debugging output in there):

tea (organisation *)$ ./tea orgs ls
2020/12/05 22:11:37 GlobalLoginValue: {}%!(EXTRA string=)
2020/12/05 22:11:37 : {}%!(EXTRA *gitea.User=&{1 administrator  giteaadmin@soebes.de http://localhost:3000/user/avatar/administrator/-1 en-US true 2020-12-04 21:17:01 +0000 UTC 2020-12-04 21:16:54 +0000 UTC})
2020/12/05 22:11:37 Login.Name {}%!(EXTRA string=admin)
2020/12/05 22:11:37 Info.Username {}%!(EXTRA string=administrator)
+----+------+---------------+----------------------------+---------------------+------------------------+
| ID | NAME |   FULLNAME    |          WEBSITE           |      LOCATION       |      DESCRIPTION       |
+----+------+---------------+----------------------------+---------------------+------------------------+
|  3 | test | Org Full Name | http://www.site-of-the.org | Location of the org | Description of the org |
+----+------+---------------+----------------------------+---------------------+------------------------+
So based on my experiments the output of `tea orgs ls` could like this: (Yes much debugging output in there): ``` tea (organisation *)$ ./tea orgs ls 2020/12/05 22:11:37 GlobalLoginValue: {}%!(EXTRA string=) 2020/12/05 22:11:37 : {}%!(EXTRA *gitea.User=&{1 administrator giteaadmin@soebes.de http://localhost:3000/user/avatar/administrator/-1 en-US true 2020-12-04 21:17:01 +0000 UTC 2020-12-04 21:16:54 +0000 UTC}) 2020/12/05 22:11:37 Login.Name {}%!(EXTRA string=admin) 2020/12/05 22:11:37 Info.Username {}%!(EXTRA string=administrator) +----+------+---------------+----------------------------+---------------------+------------------------+ | ID | NAME | FULLNAME | WEBSITE | LOCATION | DESCRIPTION | +----+------+---------------+----------------------------+---------------------+------------------------+ | 3 | test | Org Full Name | http://www.site-of-the.org | Location of the org | Description of the org | +----+------+---------------+----------------------------+---------------------+------------------------+ ```

In theory both tea admin orgs... and tea orgs... should work, but just like how we have the api split up they would serve different situations, even though they may be largely similar.

In theory both `tea admin orgs...` and `tea orgs...` should work, but just like how we have the api split up they would serve different situations, even though they may be largely similar.
Author
Member

In theory both tea admin orgs... and tea orgs... should work, but just like how we have the api split up they would serve different situations, even though they may be largely similar.

So admin orgs .. as I described in #161 and separate tea orgs .. ok..I thought so ..but wanted to be sure...

> In theory both `tea admin orgs...` and `tea orgs...` should work, but just like how we have the api split up they would serve different situations, even though they may be largely similar. So `admin orgs ..` as I described in #161 and separate `tea orgs ..` ok..I thought so ..but wanted to be sure...
Owner

admin orgs is only if you have admin access ...

admin orgs is only if you have admin access ...
noerw added the
status/has-pull
label 2020-12-06 11:56:51 +00:00
noerw added this to the v0.6.0 milestone 2020-12-06 11:56:55 +00:00
noerw added the
kind
feature
label 2020-12-06 11:57:07 +00:00
6543 closed this issue 2020-12-06 22:02:50 +00:00
6543 closed this issue 2020-12-06 22:02:50 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#263
No description provided.