jfrog / jfrog/log-analytics-splunk

no template "artifactory.getImageInfoByValue" associated with template "gotpl"

Open
#80 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I'm trying to add the contents of the artifactory-ha-values.yaml to an existing artifactory-ha deployment, which is running in an ArgoCD app, and am encountering the following error:

Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = `helm template . --name-template jfrog-artifactory-ha-<redacted> --namespace artifactory --kube-version 1.30 --values /tmp/<redacted> <api versions removed> --include-crds` failed exit status 1: Error: template: artifactory-ha/templates/artifactory-primary-statefulset.yaml:108:3: executing "artifactory-ha/templates/artifactory-primary-statefulset.yaml" at <tpl (include "artifactory-ha.customInitContainersBegin" .) .>: error calling tpl: error during tpl function execution for "- name: \"prepare-fluentd-conf-on-persistent-volume\"\n image: {{ include \"artifactory.getImageInfoByValue\" (list . \"initContainers\") }}\n imagePullPolicy: \"{{ .Values.artifactory.image.pullPolicy }}\"\n command:\n - 'sh'\n - '-c'\n - >\n mkdir -p {{ .Values.artifactory.persistence.mountPath }}/etc/fluentd/;\n curl https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/fluent.conf.rt -o {{ .Values.artifactory.persistence.mountPath }}/etc/fluentd/fluentd.conf\n volumeMounts:\n - mountPath: \"{{ .Values.artifactory.persistence.mountPath }}\"\n name: volume\n": template: gotpl:2:12: executing "gotpl" at <include "artifactory.getImageInfoByValue" (list . "initContainers")>: error calling include: template: no template "artifactory.getImageInfoByValue" associated with template "gotpl" Use --debug flag to render out invalid YAML

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with helm/artifactory-ha-values.yaml and helm/artifactory-ha/templates/artifactory-primary-statefulset.yaml, then reproduce the reported helm template command with --debug. Trace the custom init-container template and determine why artifactory.getImageInfoByValue is unavailable; done means the chart renders valid manifests for these values.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.