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: README.md
+37-10Lines changed: 37 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,13 @@ jit-customer-scripts/
36
36
- Python 3.x
37
37
- Git
38
38
39
+
## Generating API Keys
40
+
41
+
* To generate Github Personal Access Token(PAT) refer to
42
+
this [guide](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic)
43
+
* To generate a Jit API Key Go to Settings -> Users & Permissions -> API Tokens in your
44
+
Jit [dashboard](https://platform.jit.io).
45
+
39
46
## Installation
40
47
41
48
1. Clone the repository:
@@ -84,23 +91,29 @@ make create-teams
84
91
85
92
This command is a convenience utility that extracts the teams to generate from Github topics. \
This command will fetch the repository names and topics from the GitHub API and generate the JSON file. And then it will create the teams and update the assets.
100
+
This command will fetch the repository names and topics from the GitHub API and generate the JSON file. And then it will
101
+
create the teams and update the assets.
93
102
94
103
### Using External JSON File
95
104
96
-
You can also provide a JSON file containing team details using the `--input` argument. The JSON file should have the following structure:
105
+
You can also provide a JSON file containing team details using a command line argument directly. The JSON file should
106
+
have the following structure:
97
107
98
108
```json
99
109
{
100
110
"teams": [
101
111
{
102
112
"name": "Team 1",
103
-
"members": ["user1", "user2"],
113
+
"members": [
114
+
"user1",
115
+
"user2"
116
+
],
104
117
"resources": [
105
118
{
106
119
"type": "{resource_type}",
@@ -114,7 +127,10 @@ You can also provide a JSON file containing team details using the `--input` arg
114
127
},
115
128
{
116
129
"name": "Team 2",
117
-
"members": ["user3", "user4"],
130
+
"members": [
131
+
"user3",
132
+
"user4"
133
+
],
118
134
"resources": [
119
135
{
120
136
"type": "{resource_type}",
@@ -126,16 +142,27 @@ You can also provide a JSON file containing team details using the `--input` arg
126
142
}
127
143
```
128
144
129
-
To use the `--input` argument, run the following command:
Replace `path/to/teams.json` with the actual path to your JSON file.
136
152
137
-
## Development
153
+
## Excluding Topics
154
+
155
+
You can exclude certain topics from being considered when creating teams. \
156
+
To exclude topics, you could add them in the `make configure` command or update this env var in
157
+
the `.env` file: `TEAM_WILDCARD_TO_EXCLUDE`.
138
158
139
-
To override the default Frontegg authentication endpoint, you can set the `FRONTEGG_AUTH_ENDPOINT` environment variable. If the variable is not set, the default value will be used.
159
+
For example, to exclude topics that contain the word "test", you can set the variable as follows:
160
+
161
+
TEAM_WILDCARD_TO_EXCLUDE=*test*
162
+
163
+
This will exclude topics with names like "test", "test123", and "abc-testing".
164
+
165
+
## Development
140
166
141
-
To override Jit's API endpoint, you can set the `JIT_API_ENDPOINT` environment variable. If the variable is not set, the default value will be used.
167
+
To override Jit's API endpoint, you can set the `JIT_API_ENDPOINT` environment variable. If the variable is not set, the
0 commit comments