List the CI secrets and variables
GET
/api/v3/organizations/{organisation}/ci/values
const url = 'https://dashboard.quantcdn.io/api/v3/organizations/test-org/ci/values?repo=acme%2Fweb';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://dashboard.quantcdn.io/api/v3/organizations/test-org/ci/values?repo=acme%2Fweb' \ --header 'Authorization: Bearer <token>'Returns the organisation’s CI values and, without the repo filter, every repository’s values. A variable carries its value. A secret never does. Quant gives the values to CI jobs on the organisation’s runner pools as environment variables, so a workflow uses ${{ env.NAME }} instead of ${{ secrets.NAME }}. Needs the cloud:read scope and the CI runners feature.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”organisation
required
string
The organisation ID
Example
test-orgQuery Parameters
Section titled “Query Parameters”repo
string
Only the organisation’s values and this repository’s values. Lower-cased by the server.
Example
acme/webResponses
Section titled “Responses”The values
Media typeapplication/json
object
values
Array<object>
CI secret or variableobject
name
string
kind
string
scope
string
repo
Lower-case owner/name. Present when scope is repo.
string
branches
The branch rule. Absent when the value applies to every branch.
Array<string>
updatedAt
string format: date-time
updatedBy
string
value
Variables only. A secret value is never returned.
string
Example
{ "values": [ { "name": "DEPLOY_KEY", "kind": "secret", "scope": "org", "repo": "acme/web" } ]}The organisation does not have CI runners
