Accept special character in yaml key

[olblak]

Accepts special characters in YAML key names.

Remark:
In the current state, a key like agents[0] will always be considered as a position in the array 'agents' instead of a key named 'agents[0]'.

Signed-off-by: Olivier Vernin olivier@vernin.me

[jetersen]

Ha I was just about to create an issue 😅

This case is not working for me:

source:
  kind: githubRelease
  spec:
    owner: "argoproj"
    repository: "argo-cd"
    token: "{{ requiredEnv .github.token }}"
    username: "{{ .github.username }}"
    version: "latest"
targets:
  argocd:
    name: argo-cd
    kind: yaml
    prefix: 'https://github.com/argoproj/argo-cd/manifests/cluster-install?ref='
    spec:
      prefix: 'https://github.com/argoproj/argo-cd/manifests/cluster-install?ref='
      file: "apps/argocd/kustomization.yaml"
      key: "bases[0]"
    scm:
      github:
        user: "{{ .github.user }}"
        email: "{{ .github.email }}"
        owner: "{{ .github.owner }}"
        repository: "{{ .github.repository }}"
        token: "{{ requiredEnv .github.token }}"
        username: "{{ .github.username }}"
        branch: "{{ .github.branch }}"

[olblak]

Ha I was just about to create an issue sweat_smile

This case is not working for me:

source:
  kind: githubRelease
  spec:
    owner: "argoproj"
    repository: "argo-cd"
    token: "{{ requiredEnv .github.token }}"
    username: "{{ .github.username }}"
    version: "latest"
targets:
  argocd:
    name: argo-cd
    kind: yaml
    prefix: 'https://github.com/argoproj/argo-cd/manifests/cluster-install?ref='
    spec:
      prefix: 'https://github.com/argoproj/argo-cd/manifests/cluster-install?ref='
      file: "apps/argocd/kustomization.yaml"
      key: "bases[0]"
    scm:
      github:
        user: "{{ .github.user }}"
        email: "{{ .github.email }}"
        owner: "{{ .github.owner }}"
        repository: "{{ .github.repository }}"
        token: "{{ requiredEnv .github.token }}"
        username: "{{ .github.username }}"
        branch: "{{ .github.branch }}"

Your case is definitely a bug as it should already be working. At least I am using similar configuration.

The current PR is to automate key value that looks like this ''