This Concourse resource allows you to track the version of an Instana backend.
-
endpoint: Required. The URL of your Instana backend, including the protocol (https) and, with self-managed (a.k.a. on-prem) units, the port; do not include the path. So,https://my-unit.instana.ioorhttps://my-unit.my-domain:1444are good,https://my-unit.instana.io/apiis not. -
api_token: A valid API token, no additional permissions required.
resource_types:
- name: instana-version
type: registry-image
source:
repository: icr.io/instana/instana-version-resource
tag: latest
resources:
- name: backend-version
type: instana-version
source:
endpoint: https://awesome-tenant.instana.io
api_token: ((instana_api_token)) # Use secrets if you can!
granularity: minor # optional, defaults to ""; valid values are: 'branch', 'full', 'major', 'minor' or 'patch'
format: # optional, defaults to "%branch%"Supports the following parameters:
-
formatprovides a formatting pattern for the release. The following tokens are replaced in the provided format string:%branch%will be replaced with the currently deployed release branch, e.g.191%full%will be replaced with the currently deployed major version e.g.2%major%will be replaced with the currently deployed minor version e.g.191%patch%will be replaced with the currently deployed patch version e.g.519-0
-
granularityprovides short-hands forformatas follows:branch->%branch%full->%full%major->%major%.%minor%patch->%major%.%minor%.%patch%
Note: Using both format and granularity is not allowed, and the resource will fail.
The resource will create the following file:
release, containing the formatted version based on the value of theformatparameterimage_tag, the full version, e.g.2.191.519-0branch, the currently deployed release branch, e.g.191major, the currently deployed major version e.g.2minor, the currently deployed minor version e.g.191patch, the currently deployed patch version e.g.519-0
To ensure we do not miss your requests, we disabled the Issues functionality for this repository. If you have questions about how to use Concourse resource, please open a support request.
The actions of the resource are written in bash, curl and jq, with the goal of being easy to debug in local even from inside a Docker image (hello, fly intercept!).
The test scripts assumes a local Docker daemon.
Ah, our kind of person! Go ahead, open a Pull Request.
Please be aware that we will be able to accept only code contributed under the Apache 2.0 license.