Skip to content
enodia

Bamboo

Data Center only — Atlassian Cloud does not expose the endpoint this probe reads. Reads GET /rest/applinks/1.0/manifest, the same Application Links manifest every Atlassian Data Center product exposes — anonymous, which is why it’s used instead of /rest/api/2/serverInfo.

targets:
  - id: bamboo-main
    product: bamboo
    address: https://bamboo.example.com

Authentication

Section titled “Authentication”

Optional — the manifest is readable without credentials. none, basic, and bearer are all accepted if you’d rather authenticate anyway.

Vendor identity check

Section titled “Vendor identity check”

The manifest’s <typeId> is compared against what product: bamboo expects (bamboo). A URL that turns out to be Jira or Confluence fails loudly instead of getting recorded as a wrong fact — see Jira, Confluence, Bitbucket for the sibling products sharing this same manifest convention.

Recorded fields

Section titled “Recorded fields”
  • version
  • extra.buildNumber, extra.typeId — typeId will read bamboo

Lifecycle resolver

Section titled “Lifecycle resolver”

None — endoflife.date has no Bamboo calendar. enodia still tracks version and buildNumber; only the lifecycle axis stays unknown.