airbyte-source-gitlab 4.0.1__tar.gz → 4.0.3__tar.gz

Sign up to get free protection for your applications and to get access to all the features.
Files changed (39) hide show
  1. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/PKG-INFO +26 -12
  2. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/README.md +24 -11
  3. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/pyproject.toml +2 -2
  4. airbyte_source_gitlab-4.0.3/source_gitlab/schemas/branches.json +51 -0
  5. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/commits.json +21 -0
  6. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/deployments.json +61 -0
  7. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/epic_issues.json +51 -0
  8. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/epics.json +39 -0
  9. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/group_issue_boards.json +21 -0
  10. airbyte_source_gitlab-4.0.3/source_gitlab/schemas/group_labels.json +50 -0
  11. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/group_milestones.json +12 -0
  12. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/groups.json +51 -0
  13. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/issues.json +87 -0
  14. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/jobs.json +31 -0
  15. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/merge_request_commits.json +22 -0
  16. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/merge_requests.json +60 -0
  17. airbyte_source_gitlab-4.0.3/source_gitlab/schemas/pipelines.json +52 -0
  18. airbyte_source_gitlab-4.0.3/source_gitlab/schemas/pipelines_extended.json +129 -0
  19. airbyte_source_gitlab-4.0.3/source_gitlab/schemas/project_labels.json +58 -0
  20. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/project_milestones.json +12 -0
  21. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/projects.json +163 -0
  22. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/releases.json +22 -0
  23. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/tags.json +10 -0
  24. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/users.json +7 -0
  25. airbyte_source_gitlab-4.0.1/source_gitlab/schemas/branches.json +0 -40
  26. airbyte_source_gitlab-4.0.1/source_gitlab/schemas/group_labels.json +0 -39
  27. airbyte_source_gitlab-4.0.1/source_gitlab/schemas/pipelines.json +0 -41
  28. airbyte_source_gitlab-4.0.1/source_gitlab/schemas/pipelines_extended.json +0 -100
  29. airbyte_source_gitlab-4.0.1/source_gitlab/schemas/project_labels.json +0 -45
  30. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/__init__.py +0 -0
  31. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/components/partition_routers.py +0 -0
  32. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/config_migrations.py +0 -0
  33. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/manifest.yaml +0 -0
  34. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/run.py +0 -0
  35. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/group_members.json +0 -0
  36. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/schemas/project_members.json +0 -0
  37. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/source.py +0 -0
  38. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/spec.json +0 -0
  39. {airbyte_source_gitlab-4.0.1 → airbyte_source_gitlab-4.0.3}/source_gitlab/utils.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: airbyte-source-gitlab
3
- Version: 4.0.1
3
+ Version: 4.0.3
4
4
  Summary: Source implementation for GitLab.
5
5
  Home-page: https://airbyte.com
6
6
  License: MIT
@@ -12,7 +12,7 @@ Classifier: Programming Language :: Python :: 3
12
12
  Classifier: Programming Language :: Python :: 3.9
13
13
  Classifier: Programming Language :: Python :: 3.10
14
14
  Classifier: Programming Language :: Python :: 3.11
15
- Requires-Dist: airbyte-cdk (>=0,<1)
15
+ Requires-Dist: airbyte-cdk (==0.80.0)
16
16
  Requires-Dist: vcrpy (==4.1.1)
17
17
  Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/gitlab
18
18
  Project-URL: Repository, https://github.com/airbytehq/airbyte
@@ -20,32 +20,33 @@ Description-Content-Type: text/markdown
20
20
 
21
21
  # Gitlab source connector
22
22
 
23
-
24
23
  This is the repository for the Gitlab source connector, written in Python.
25
24
  For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/gitlab).
26
25
 
27
26
  ## Local development
28
27
 
29
28
  ### Prerequisites
30
- * Python (~=3.9)
31
- * Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
32
29
 
30
+ - Python (~=3.9)
31
+ - Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
33
32
 
34
33
  ### Installing the connector
34
+
35
35
  From this connector directory, run:
36
+
36
37
  ```bash
37
38
  poetry install --with dev
38
39
  ```
39
40
 
40
-
41
41
  ### Create credentials
42
+
42
43
  **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/gitlab)
43
44
  to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_gitlab/spec.yaml` file.
44
45
  Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
45
46
  See `sample_files/sample_config.json` for a sample config file.
46
47
 
47
-
48
48
  ### Locally running the connector
49
+
49
50
  ```
50
51
  poetry run source-gitlab spec
51
52
  poetry run source-gitlab check --config secrets/config.json
@@ -54,23 +55,28 @@ poetry run source-gitlab read --config secrets/config.json --catalog integration
54
55
  ```
55
56
 
56
57
  ### Running unit tests
58
+
57
59
  To run unit tests locally, from the connector directory run:
60
+
58
61
  ```
59
62
  poetry run pytest unit_tests
60
63
  ```
61
64
 
62
65
  ### Building the docker image
66
+
63
67
  1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
64
68
  2. Run the following command to build the docker image:
69
+
65
70
  ```bash
66
71
  airbyte-ci connectors --name=source-gitlab build
67
72
  ```
68
73
 
69
74
  An image will be available on your host with the tag `airbyte/source-gitlab:dev`.
70
75
 
71
-
72
76
  ### Running as a docker container
77
+
73
78
  Then run any of the connector commands as follows:
79
+
74
80
  ```
75
81
  docker run --rm airbyte/source-gitlab:dev spec
76
82
  docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-gitlab:dev check --config /secrets/config.json
@@ -79,18 +85,23 @@ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integrat
79
85
  ```
80
86
 
81
87
  ### Running our CI test suite
88
+
82
89
  You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
90
+
83
91
  ```bash
84
92
  airbyte-ci connectors --name=source-gitlab test
85
93
  ```
86
94
 
87
95
  ### Customizing acceptance Tests
96
+
88
97
  Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
89
98
  If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
90
99
 
91
100
  ### Dependency Management
92
- All of your dependencies should be managed via Poetry.
101
+
102
+ All of your dependencies should be managed via Poetry.
93
103
  To add a new dependency, run:
104
+
94
105
  ```bash
95
106
  poetry add <package-name>
96
107
  ```
@@ -98,14 +109,17 @@ poetry add <package-name>
98
109
  Please commit the changes to `pyproject.toml` and `poetry.lock` files.
99
110
 
100
111
  ## Publishing a new version of the connector
112
+
101
113
  You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
114
+
102
115
  1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-gitlab test`
103
- 2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)):
104
- - bump the `dockerImageTag` value in in `metadata.yaml`
105
- - bump the `version` value in `pyproject.toml`
116
+ 2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)):
117
+ - bump the `dockerImageTag` value in in `metadata.yaml`
118
+ - bump the `version` value in `pyproject.toml`
106
119
  3. Make sure the `metadata.yaml` content is up to date.
107
120
  4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/gitlab.md`).
108
121
  5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
109
122
  6. Pat yourself on the back for being an awesome contributor.
110
123
  7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
111
124
  8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
125
+
@@ -1,31 +1,32 @@
1
1
  # Gitlab source connector
2
2
 
3
-
4
3
  This is the repository for the Gitlab source connector, written in Python.
5
4
  For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/gitlab).
6
5
 
7
6
  ## Local development
8
7
 
9
8
  ### Prerequisites
10
- * Python (~=3.9)
11
- * Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
12
9
 
10
+ - Python (~=3.9)
11
+ - Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
13
12
 
14
13
  ### Installing the connector
14
+
15
15
  From this connector directory, run:
16
+
16
17
  ```bash
17
18
  poetry install --with dev
18
19
  ```
19
20
 
20
-
21
21
  ### Create credentials
22
+
22
23
  **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/gitlab)
23
24
  to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_gitlab/spec.yaml` file.
24
25
  Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
25
26
  See `sample_files/sample_config.json` for a sample config file.
26
27
 
27
-
28
28
  ### Locally running the connector
29
+
29
30
  ```
30
31
  poetry run source-gitlab spec
31
32
  poetry run source-gitlab check --config secrets/config.json
@@ -34,23 +35,28 @@ poetry run source-gitlab read --config secrets/config.json --catalog integration
34
35
  ```
35
36
 
36
37
  ### Running unit tests
38
+
37
39
  To run unit tests locally, from the connector directory run:
40
+
38
41
  ```
39
42
  poetry run pytest unit_tests
40
43
  ```
41
44
 
42
45
  ### Building the docker image
46
+
43
47
  1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
44
48
  2. Run the following command to build the docker image:
49
+
45
50
  ```bash
46
51
  airbyte-ci connectors --name=source-gitlab build
47
52
  ```
48
53
 
49
54
  An image will be available on your host with the tag `airbyte/source-gitlab:dev`.
50
55
 
51
-
52
56
  ### Running as a docker container
57
+
53
58
  Then run any of the connector commands as follows:
59
+
54
60
  ```
55
61
  docker run --rm airbyte/source-gitlab:dev spec
56
62
  docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-gitlab:dev check --config /secrets/config.json
@@ -59,18 +65,23 @@ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integrat
59
65
  ```
60
66
 
61
67
  ### Running our CI test suite
68
+
62
69
  You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
70
+
63
71
  ```bash
64
72
  airbyte-ci connectors --name=source-gitlab test
65
73
  ```
66
74
 
67
75
  ### Customizing acceptance Tests
76
+
68
77
  Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
69
78
  If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
70
79
 
71
80
  ### Dependency Management
72
- All of your dependencies should be managed via Poetry.
81
+
82
+ All of your dependencies should be managed via Poetry.
73
83
  To add a new dependency, run:
84
+
74
85
  ```bash
75
86
  poetry add <package-name>
76
87
  ```
@@ -78,14 +89,16 @@ poetry add <package-name>
78
89
  Please commit the changes to `pyproject.toml` and `poetry.lock` files.
79
90
 
80
91
  ## Publishing a new version of the connector
92
+
81
93
  You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
94
+
82
95
  1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-gitlab test`
83
- 2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)):
84
- - bump the `dockerImageTag` value in in `metadata.yaml`
85
- - bump the `version` value in `pyproject.toml`
96
+ 2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)):
97
+ - bump the `dockerImageTag` value in in `metadata.yaml`
98
+ - bump the `version` value in `pyproject.toml`
86
99
  3. Make sure the `metadata.yaml` content is up to date.
87
100
  4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/gitlab.md`).
88
101
  5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
89
102
  6. Pat yourself on the back for being an awesome contributor.
90
103
  7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
91
- 8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
104
+ 8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
@@ -5,7 +5,7 @@ requires = [
5
5
  build-backend = "poetry.core.masonry.api"
6
6
 
7
7
  [tool.poetry]
8
- version = "4.0.1"
8
+ version = "4.0.3"
9
9
  name = "airbyte-source-gitlab"
10
10
  description = "Source implementation for GitLab."
11
11
  authors = [
@@ -22,7 +22,7 @@ packages = [
22
22
 
23
23
  [tool.poetry.dependencies]
24
24
  python = "^3.9,<3.12"
25
- airbyte-cdk = "^0"
25
+ airbyte-cdk = "0.80.0"
26
26
  vcrpy = "==4.1.1"
27
27
 
28
28
  [tool.poetry.scripts]
@@ -0,0 +1,51 @@
1
+ {
2
+ "$schema": "https://json-schema.org/draft-07/schema#",
3
+ "type": "object",
4
+ "properties": {
5
+ "project_id": {
6
+ "description": "ID of the project to which this branch belongs.",
7
+ "type": ["null", "integer"]
8
+ },
9
+ "name": {
10
+ "description": "Name of the branch.",
11
+ "type": ["null", "string"]
12
+ },
13
+ "merged": {
14
+ "description": "Indicates if the changes in this branch have been merged into another branch.",
15
+ "type": ["null", "boolean"]
16
+ },
17
+ "protected": {
18
+ "description": "Indicates if the branch is protected to prevent direct pushes.",
19
+ "type": ["null", "boolean"]
20
+ },
21
+ "developers_can_push": {
22
+ "description": "Indicates if developers can push changes to this branch.",
23
+ "type": ["null", "boolean"]
24
+ },
25
+ "developers_can_merge": {
26
+ "description": "Indicates if developers can merge changes to this branch.",
27
+ "type": ["null", "boolean"]
28
+ },
29
+ "can_push": {
30
+ "description": "Indicates if the user has permission to push changes to this branch.",
31
+ "type": ["null", "boolean"]
32
+ },
33
+ "default": {
34
+ "description": "Indicates if this is the default branch of the project.",
35
+ "type": ["null", "boolean"]
36
+ },
37
+ "web_url": {
38
+ "description": "URL to view the branch in a web browser.",
39
+ "type": ["null", "string"]
40
+ },
41
+ "commit_id": {
42
+ "description": "ID of the commit associated with this branch.",
43
+ "type": ["null", "string"]
44
+ },
45
+ "commit": {
46
+ "description": "Details about the commit associated with this branch.",
47
+ "type": ["null", "object"],
48
+ "additionalProperties": true
49
+ }
50
+ }
51
+ }
@@ -3,44 +3,56 @@
3
3
  "type": "object",
4
4
  "properties": {
5
5
  "project_id": {
6
+ "description": "ID of the project to which the commit belongs.",
6
7
  "type": ["null", "integer"]
7
8
  },
8
9
  "id": {
10
+ "description": "Unique identifier of the commit.",
9
11
  "type": ["null", "string"]
10
12
  },
11
13
  "short_id": {
14
+ "description": "Shortened version of the commit's unique identifier.",
12
15
  "type": ["null", "string"]
13
16
  },
14
17
  "created_at": {
18
+ "description": "Date and time when the commit record was created.",
15
19
  "type": ["null", "string"],
16
20
  "format": "date-time"
17
21
  },
18
22
  "parent_ids": {
23
+ "description": "Array of unique identifiers of parent commits if the commit has multiple parents.",
19
24
  "type": ["null", "array"],
20
25
  "items": {
21
26
  "type": ["null", "string"]
22
27
  }
23
28
  },
24
29
  "title": {
30
+ "description": "Title or summary of the commit message.",
25
31
  "type": ["null", "string"]
26
32
  },
27
33
  "message": {
34
+ "description": "Description or text message associated with the commit.",
28
35
  "type": ["null", "string"]
29
36
  },
30
37
  "author_name": {
38
+ "description": "Name of the author who created the commit.",
31
39
  "type": ["null", "string"]
32
40
  },
33
41
  "author_email": {
42
+ "description": "Email of the author who created the commit.",
34
43
  "type": ["null", "string"]
35
44
  },
36
45
  "authored_date": {
46
+ "description": "Date and time when the commit was authored.",
37
47
  "type": ["null", "string"],
38
48
  "format": "date-time"
39
49
  },
40
50
  "extended_trailers": {
51
+ "description": "Additional information or metadata added to the commit. Eg: 'Cc' field for carbon copy email addresses.",
41
52
  "type": ["null", "object"],
42
53
  "properties": {
43
54
  "Cc": {
55
+ "description": "Carbon copy email addresses associated with the commit.",
44
56
  "type": ["null", "array"],
45
57
  "items": {
46
58
  "type": ["null", "string"]
@@ -49,31 +61,40 @@
49
61
  }
50
62
  },
51
63
  "committer_name": {
64
+ "description": "Name of the committer who committed the changes.",
52
65
  "type": ["null", "string"]
53
66
  },
54
67
  "committer_email": {
68
+ "description": "Email of the committer who committed the changes.",
55
69
  "type": ["null", "string"]
56
70
  },
57
71
  "committed_date": {
72
+ "description": "Date and time when the commit was committed.",
58
73
  "type": ["null", "string"],
59
74
  "format": "date-time"
60
75
  },
61
76
  "trailers": {
77
+ "description": "Metadata information provided below the commit message.",
62
78
  "type": ["null", "object"]
63
79
  },
64
80
  "web_url": {
81
+ "description": "URL link to view the commit details in a web browser.",
65
82
  "type": ["null", "string"]
66
83
  },
67
84
  "stats": {
85
+ "description": "Statistics related to the commit changes like additions, deletions, and total changes.",
68
86
  "type": ["null", "object"],
69
87
  "properties": {
70
88
  "additions": {
89
+ "description": "Number of lines added in the commit.",
71
90
  "type": ["null", "integer"]
72
91
  },
73
92
  "deletions": {
93
+ "description": "Number of lines deleted in the commit.",
74
94
  "type": ["null", "integer"]
75
95
  },
76
96
  "total": {
97
+ "description": "Total number of lines changed in the commit.",
77
98
  "type": ["null", "integer"]
78
99
  }
79
100
  }
@@ -3,203 +3,264 @@
3
3
  "type": "object",
4
4
  "properties": {
5
5
  "id": {
6
+ "description": "Unique identifier of the deployment",
6
7
  "type": ["null", "integer"]
7
8
  },
8
9
  "iid": {
10
+ "description": "Identification number of the deployment",
9
11
  "type": ["null", "integer"]
10
12
  },
11
13
  "status": {
14
+ "description": "Status of the deployment",
12
15
  "type": ["null", "string"]
13
16
  },
14
17
  "ref": {
18
+ "description": "Reference of the deployment",
15
19
  "type": ["null", "string"]
16
20
  },
17
21
  "sha": {
22
+ "description": "SHA of the deployment",
18
23
  "type": ["null", "string"]
19
24
  },
20
25
  "environment_name": {
26
+ "description": "Name of the environment",
21
27
  "type": ["null", "string"]
22
28
  },
23
29
  "created_at": {
30
+ "description": "The timestamp when the deployment was created",
24
31
  "type": ["null", "string"],
25
32
  "format": "date-time"
26
33
  },
27
34
  "updated_at": {
35
+ "description": "Timestamp when the deployment was last updated",
28
36
  "type": ["null", "string"],
29
37
  "format": "date-time"
30
38
  },
31
39
  "user": {
40
+ "description": "User associated with the deployment",
32
41
  "type": ["null", "object"],
33
42
  "additionalProperties": true
34
43
  },
35
44
  "user_full_name": {
45
+ "description": "Full name of the user associated with the deployment",
36
46
  "type": ["null", "string"]
37
47
  },
38
48
  "user_username": {
49
+ "description": "Username of the user associated with the deployment",
39
50
  "type": ["null", "string"]
40
51
  },
41
52
  "user_id": {
53
+ "description": "Unique identifier of the user associated with the deployment",
42
54
  "type": ["null", "integer"]
43
55
  },
44
56
  "environment": {
57
+ "description": "Environment information of the deployment",
45
58
  "type": ["null", "object"],
46
59
  "additionalProperties": true
47
60
  },
48
61
  "environment_id": {
62
+ "description": "Unique identifier of the environment",
49
63
  "type": ["null", "integer"]
50
64
  },
51
65
  "project_id": {
66
+ "description": "Unique identifier of the project",
52
67
  "type": ["null", "integer"]
53
68
  },
54
69
  "deployable": {
70
+ "description": "Details of the deployment job",
55
71
  "type": ["null", "object"],
56
72
  "properties": {
57
73
  "commit": {
74
+ "description": "Information about the commit associated with the deployment",
58
75
  "type": ["null", "object"],
59
76
  "properties": {
60
77
  "author_email": {
78
+ "description": "Email of the author of the commit",
61
79
  "type": ["null", "string"]
62
80
  },
63
81
  "author_name": {
82
+ "description": "Name of the author of the commit",
64
83
  "type": ["null", "string"]
65
84
  },
66
85
  "created_at": {
86
+ "description": "Timestamp when the commit was created",
67
87
  "type": ["null", "string"],
68
88
  "format": "date-time"
69
89
  },
70
90
  "id": {
91
+ "description": "Unique identifier of the commit",
71
92
  "type": ["null", "string"]
72
93
  },
73
94
  "message": {
95
+ "description": "Message associated with the commit",
74
96
  "type": ["null", "string"]
75
97
  },
76
98
  "short_id": {
99
+ "description": "Short identifier of the commit",
77
100
  "type": ["null", "string"]
78
101
  },
79
102
  "title": {
103
+ "description": "Title of the commit",
80
104
  "type": ["null", "string"]
81
105
  }
82
106
  }
83
107
  },
84
108
  "coverage": {
109
+ "description": "Coverage information of the deployment",
85
110
  "type": ["null", "string"]
86
111
  },
87
112
  "created_at": {
113
+ "description": "Timestamp when the deployment was created",
88
114
  "type": ["null", "string"],
89
115
  "format": "date-time"
90
116
  },
91
117
  "finished_at": {
118
+ "description": "Timestamp when the deployment was finished",
92
119
  "type": ["null", "string"],
93
120
  "format": "date-time"
94
121
  },
95
122
  "id": {
123
+ "description": "Unique identifier of the deployment",
96
124
  "type": ["null", "integer"]
97
125
  },
98
126
  "name": {
127
+ "description": "Name of the deployment",
99
128
  "type": ["null", "string"]
100
129
  },
101
130
  "ref": {
131
+ "description": "Reference of the deployment",
102
132
  "type": ["null", "string"]
103
133
  },
104
134
  "runner": {
135
+ "description": "Runner information for the deployment",
105
136
  "type": ["null", "string"]
106
137
  },
107
138
  "stage": {
139
+ "description": "Stage of the deployment",
108
140
  "type": ["null", "string"]
109
141
  },
110
142
  "started_at": {
143
+ "description": "Timestamp when the deployment was started",
111
144
  "type": ["null", "string"],
112
145
  "format": "date-time"
113
146
  },
114
147
  "status": {
148
+ "description": "Status of the deployment",
115
149
  "type": ["null", "string"]
116
150
  },
117
151
  "tag": {
152
+ "description": "Tag information for the deployment",
118
153
  "type": ["null", "boolean"]
119
154
  },
120
155
  "project": {
156
+ "description": "Details of the project where the deployment occurred",
121
157
  "type": ["null", "object"],
122
158
  "properties": {
123
159
  "ci_job_token_scope_enabled": {
160
+ "description": "Flag indicating if the CI job token scope is enabled for the project",
124
161
  "type": ["null", "boolean"]
125
162
  }
126
163
  }
127
164
  },
128
165
  "user": {
166
+ "description": "User associated with the deployment",
129
167
  "type": ["null", "object"],
130
168
  "properties": {
131
169
  "id": {
170
+ "description": "Unique identifier of the user",
132
171
  "type": ["null", "integer"]
133
172
  },
134
173
  "name": {
174
+ "description": "Name of the user",
135
175
  "type": ["null", "string"]
136
176
  },
137
177
  "username": {
178
+ "description": "Username of the user",
138
179
  "type": ["null", "string"]
139
180
  },
140
181
  "state": {
182
+ "description": "State information of the user",
141
183
  "type": ["null", "string"]
142
184
  },
143
185
  "avatar_url": {
186
+ "description": "URL of the user's avatar",
144
187
  "type": ["null", "string"]
145
188
  },
146
189
  "web_url": {
190
+ "description": "URL for accessing the user's information",
147
191
  "type": ["null", "string"]
148
192
  },
149
193
  "created_at": {
194
+ "description": "Timestamp when the user was created",
150
195
  "type": ["null", "string"],
151
196
  "format": "date-time"
152
197
  },
153
198
  "bio": {
199
+ "description": "Bio information of the user",
154
200
  "type": ["null", "string"]
155
201
  },
156
202
  "location": {
203
+ "description": "Location information of the user",
157
204
  "type": ["null", "string"]
158
205
  },
159
206
  "public_email": {
207
+ "description": "Public email of the user",
160
208
  "type": ["null", "string"]
161
209
  },
162
210
  "skype": {
211
+ "description": "Skype ID of the user",
163
212
  "type": ["null", "string"]
164
213
  },
165
214
  "linkedin": {
215
+ "description": "Linkedin profile of the user",
166
216
  "type": ["null", "string"]
167
217
  },
168
218
  "twitter": {
219
+ "description": "Twitter handle of the user",
169
220
  "type": ["null", "string"]
170
221
  },
171
222
  "website_url": {
223
+ "description": "URL for the user's website",
172
224
  "type": ["null", "string"]
173
225
  },
174
226
  "organization": {
227
+ "description": "Organization information of the user",
175
228
  "type": ["null", "string"]
176
229
  }
177
230
  }
178
231
  },
179
232
  "pipeline": {
233
+ "description": "Details of the pipeline used for the deployment",
180
234
  "type": ["null", "object"],
181
235
  "properties": {
182
236
  "created_at": {
237
+ "description": "Timestamp when the pipeline associated with the deployment was created",
183
238
  "type": ["null", "string"],
184
239
  "format": "date-time"
185
240
  },
186
241
  "id": {
242
+ "description": "Unique identifier of the pipeline",
187
243
  "type": ["null", "integer"]
188
244
  },
189
245
  "ref": {
246
+ "description": "Reference of the pipeline",
190
247
  "type": ["null", "string"]
191
248
  },
192
249
  "sha": {
250
+ "description": "SHA of the pipeline",
193
251
  "type": ["null", "string"]
194
252
  },
195
253
  "status": {
254
+ "description": "Status of the pipeline",
196
255
  "type": ["null", "string"]
197
256
  },
198
257
  "updated_at": {
258
+ "description": "Timestamp when the pipeline associated with the deployment was last updated",
199
259
  "type": ["null", "string"],
200
260
  "format": "date-time"
201
261
  },
202
262
  "web_url": {
263
+ "description": "URL for accessing the pipeline in a web browser",
203
264
  "type": ["null", "string"]
204
265
  }
205
266
  }