Request to add plugins/artifact-metadata-publisher to get-default-config API
pending feedback
F
Fancy Carp
Currently the default images API https://app.harness.io/gateway/ci/execution-config/get-default-config?accountIdentifier=<$YOUR_HARNESS_ACCOUNT_ID>&infra=K8" does not list all the plugin images. Including these plugin images to the get-default-config API shall help in the following
- Identify the latest working plugin image as going by the image repository, there might be images that might be released but are not guaranteed to work. Having the images provided in the default API shall provide an idea of what latest version of the plugin works instead of users trying and testing multiple image versions
- In many instances, there are automations setup in place to pull the images from Harness public repositories to internal repositories by referring the image versions under get-default-config API. Including plugins/artifact-metadata-publisher shall help in automatic push of plugins/artifact-metadata-publisher images when a new version is available
This request is for plugins/artifact-metadata-publisher but shall benefit if other plugins are included as well.
Log In
s
shivkumar.loka
marked this post as
pending feedback
ompragash
Thanks for raising this!
Clarification on the API scope:
/gateway/ci/execution-config/get-default-config?...
returns the default image tags only for Harness CI native (OOTB) steps
. In other words, it lists the images tied to specific Harness native steps and nothing beyond that. Since plugins/artifact-metadata-publisher
isn’t used by a native step, it won’t appear in this endpoint.Status
We don’t plan to change this behavior or expand the endpoint to include additional Drone plugins.
How to handle versioning/automation
For version discovery and automation, query the plugin’s registry (or your internal mirror) and pin/approve the tags you want to use. Public tags are available here:
This keeps the API focused on native-step images while letting you control external plugin versions via your registry policy.
s
shivkumar.loka
marked this post as
under review