Skip to content

Commit 5a1f912

Browse files
committed
Proposal for versioning the ilab config file
Related to instructlab/instructlab/issues/1725 Signed-off-by: Ali Maredia <[email protected]>
1 parent 8fde6f7 commit 5a1f912

File tree

2 files changed

+26
-0
lines changed

2 files changed

+26
-0
lines changed

.spellcheck-en-custom.txt

+1
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,7 @@ hardcoded
6262
hipBLAS
6363
ilab
6464
impactful
65+
incrementing
6566
Inferencing
6667
instantiation
6768
instructlab

docs/schema/ilab-config-version.md

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# `ilab` Config.yaml Versioning
2+
3+
## Problem Statement
4+
5+
Currently the `ilab` CLI's configuration file, `config.yaml`, does not contain a version.
6+
7+
The config file in `ilab` version `0.17` cannot be used in future versions of `ilab` due to new mandatory fields and changes to existing fields.
8+
9+
As the configuration file grows, changes, and becomes more complex, versioning is necessary in order to support forwards and backwards compatibility.
10+
11+
## Proposal
12+
13+
The `ilab` configuration file has a new `version` field at the top level of the config.
14+
15+
The value of `version` should start at `1.0.0`.
16+
17+
## Future Considerations
18+
19+
As future development of `ilab` occurs, ramifications and tooling for the versioning the configuration file will need to be determined for users and developers.
20+
21+
Such considerations include but are not limited to:
22+
23+
- Rules for incrementing the version number
24+
- Tooling to support forward compatibility of configuration files
25+
- Limits for the forward and backward compatibility of configuration files

0 commit comments

Comments
 (0)