Reading issues with array elements in configuration files in DB less mode about kong

[chobits]

We need to check some updating on yaml or route validation between 2.8 and 3.4 later.

[chronolaw]

In PR #9607 we bump lyaml from 6.2.7 to 6.2.8, perhaps it causes some behaviors change.

[chronolaw]

I did a simple test:

-- resty ./t.lua
local lyaml = require "lyaml"
local contents = [[
services:
- name: local-sso
  url: https://localhost
  routes:
  - name: sso-native
    paths: [/:login, /api/frm/sso, /actuator/health]
]]
local pok, table, err = pcall(lyaml.load, contents)
assert(pok)
print(require("inspect")(table))

It works well, so I think that it is not lyaml's reason.

@lubw7 could you try the same test?

[lubw7]

Still failed, it's so queer

[chronolaw]

Could you give us a minimal test script to re-produce it?

[lubw7]

I try it in docker.io/library/kong 3.6.0, it work well.
But it failed in the image built by our team through Dockerfile.
I have checked the lyaml source code of these two images and code is identical.
So I feel puzzled why the same source code can get different running results.

I did a simple test:

-- resty ./t.lua
local lyaml = require "lyaml"
local contents = [[
services:
- name: local-sso
  url: https://localhost
  routes:
  - name: sso-native
    paths: [/:login, /api/frm/sso, /actuator/health]
]]
local pok, table, err = pcall(lyaml.load, contents)
assert(pok)
print(require("inspect")(table))

It works well, so I think that it is not lyaml's reason.

@lubw7 could you try the same test?

[github-actions]

This issue is marked as stale because it has been open for 14 days with no activity.

[github-actions]

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look
our pledge to the community
for more information.

Sincerely,
Your Kong Gateway team