-
Notifications
You must be signed in to change notification settings - Fork 845
Open
Labels
Milestone
Description
Summary
This umbrella issue tracks the migration of all remaining .config configuration files to YAML format. ATS has been progressively moving to YAML for configuration files to provide a more structured, readable, and maintainable configuration experience.
Background
Several configuration files have already been converted to YAML:
- ✅
ip_allow.yaml - ✅
jsonrpc.yaml - ✅
logging.yaml - ✅
records.yaml - ✅
sni.yaml - ✅
strategies.yaml
Remaining Configuration Files
The following files still use the legacy .config format and should be migrated to YAML:
-
cache.config→cache.yaml(see When rewriting cache.config in YAML, make it not additive. #7701) -
hosting.config→hosting.yaml -
parent.config→parent.yaml -
plugin.config→plugin.yaml -
remap.config→remap.yaml@serrislew (see ☂ Migration to remap.yaml #5590) -
socks.config→socks.yaml -
splitdns.config→splitdns.yaml -
ssl_multicert.config→ssl_multicert.yaml@bneradt (see ssl_multicert.config -> ssl_multicert.yaml #12755) -
storage.config→storage.yaml(see Changevolume.configandstorage.configtostorage.yaml#10766) -
volume.config→volume.yaml(see Changevolume.configandstorage.configtostorage.yaml#10766)
Related Issues
- ☂ Migration to remap.yaml #5590 - ☂ Migration to remap.yaml
- When rewriting cache.config in YAML, make it not additive. #7701 - When rewriting cache.config in YAML, make it not additive
- Change
volume.configandstorage.configtostorage.yaml#10766 - Changevolume.configtovolume.yaml - ☂ Remove various _filename records.config variables. #5363 - ☂ Remove various _filename records.config variables
Migration Guidelines
For each configuration file migration:
- Design a YAML schema with a consistent top-level namespace (per ☂ Proper "top level" name space for all yaml #5245)
- Implement the YAML parser alongside the existing parser
- Provide a migration script or tool for users
- Update documentation
- Deprecate the old format with appropriate warnings
- Remove the old format in a future major release
Note: these conversions should be done on the 11-Dev branch since these conversions will not be done in the 10.x release series.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status