[GH-ISSUE #4775] [Feature Request] yaml config should ignore field start with dot to support yaml merge

gitea-mirror commented

2026-05-05 14:24:57 -06:00

Owner

Originally created by @wenerme on GitHub (Apr 29, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4775

Describe the feature request

to help reuse some config like

.common: &common
  type: stcp
  secretKey: "{{.Envs.FRPC_SECRET_KEY}}"
  localIp: 127.0.0.1
  allowUsers: [ '*' ]
  transport:
    useEncryption: true
    useCompression: true

proxies:
- name: ssh
  localPort: 22
  <<: *common

- name: pg
  localPort: 5432
  <<: *common

- name: web
  localPort: 80
  <<: *common

but this is not supported by frp, this is very common pattern for docker compose yaml, github action yaml etc.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @wenerme on GitHub (Apr 29, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4775 ### Describe the feature request to help reuse some config like ```yaml .common: &common type: stcp secretKey: "{{.Envs.FRPC_SECRET_KEY}}" localIp: 127.0.0.1 allowUsers: [ '*' ] transport: useEncryption: true useCompression: true proxies: - name: ssh localPort: 22 <<: *common - name: pg localPort: 5432 <<: *common - name: web localPort: 80 <<: *common ``` but this is not supported by frp, this is very common pattern for docker compose yaml, github action yaml etc. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror closed this issue

2026-05-05 14:24:58 -06:00

gitea-mirror commented

2026-05-05 14:25:01 -06:00

Author

Owner

@fatedier commented on GitHub (May 19, 2025):

I found that the current version does support it, but you need to add the --strict-config=false startup parameter when launching.

@fatedier commented on GitHub (May 19, 2025): I found that the current version does support it, but you need to add the `--strict-config=false` startup parameter when launching.

gitea-mirror referenced this issue

2026-05-05 14:49:29 -06:00

[PR #3773] [MERGED] Strict configuration parsing #4828