yamlpath 1.24.1

Format-preserving YAML feature extraction
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

testcase:
  jobs:
    job1:
      env: &env_vars # Define the anchor on first use
        NODE_ENV: production
        DATABASE_URL: ${{ secrets.DATABASE_URL }}
      steps:
        - run: echo "Using production settings"

    job2:
      env: *env_vars # Reuse the environment variables
      steps:
        - run: echo "Same environment variables here"

    # Duplicate anchor: redefine env_vars for job3
    job3:
      env: &env_vars
        NODE_ENV: staging
        DATABASE_URL: ${{ secrets.STAGING_DB }}
      steps:
        - run: echo "Staging environment"

    job4:
      matrix: [&ver v1, *ver, &ver v2, *ver]

      env: *env_vars # Should resolve to job3's env (staging)
      steps:
        - run: echo "Also staging"


queries:
  - query: [jobs, job2, env, DATABASE_URL]
    mode: exact
    expected: "${{ secrets.DATABASE_URL }}"

  - query: [jobs, job2, env, DATABASE_URL]
    mode: key-only
    expected: "        DATABASE_URL"

  # job2 uses the first env_vars definition (production)
  - query: [jobs, job2, env, NODE_ENV]
    mode: exact
    expected: "production"

  # job4 uses the second env_vars definition (staging)
  - query: [jobs, job4, env, NODE_ENV]
    mode: exact
    expected: "staging"

  - query: [jobs, job4, env, DATABASE_URL]
    mode: exact
    expected: "${{ secrets.STAGING_DB }}"

  # Inline flow sequence with duplicate anchors
  - query: [jobs, job4, matrix, 0]
    mode: exact
    expected: "v1"

  - query: [jobs, job4, matrix, 1]
    mode: exact
    expected: "v1"

  - query: [jobs, job4, matrix, 2]
    mode: exact
    expected: "v2"

  - query: [jobs, job4, matrix, 3]
    mode: exact
    expected: "v2"