-
-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
enhancementNew feature or requestNew feature or request
Milestone
Description
Is your feature request related to a problem?
The purpose of the config endpoint such:
/api/pipeline/config/sources/api/pipeline/config/conditions/api/pipeline/config/targets
It is to identify the Git repositories linked by a specific change.
In the database, a config row contains both the Updatecli config spec and the transformers all other parameters are ignored. This is done on the Updatecli where each plugin can define the parameters to ignore
Here is an example
{
"configs": [
{
"ID": "2cecadc4-a198-4d38-8ab8-79610ac4e6f6",
"Kind": "githubrelease",
"Created_at": "2025-07-17T18:30:15.100853Z",
"Updated_at": "2025-07-17T18:30:15.100853Z",
"Config": {
"DependsOn": null,
"Name": "Get latest updatecli version",
"Kind": "githubrelease",
"Transformers": null,
"Spec": {
"Key": "tagname",
"Owner": "updatecli",
"Repository": "updatecli",
"Tag": "",
"Token": "",
"TypeFilter": {
"Draft": false,
"Latest": false,
"PreRelease": false,
"Release": false
},
"URL": "",
"Username": "",
"VersionFilter": {
"Kind": "semver",
"Pattern": "",
"Regex": "",
"Strict": false
}
},
"SCMID": "",
"DeprecatedSCMID": "",
"DeprecatedDependsOn": null
}
}
],
"total_count": 503
}
Solution you'd like
I would like a way to only return spec to make it easier to filter all similar configs
Alternatives you've considered
No response
Anything else?
No response
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Type
Projects
Status
Todo