clk extensions allow to ship configurations together
In case you need more than the traditional global vs local levels, you can create extensions.
clk extension create myextension
Created extension global/myextension.
A extension is only a subfolder inside a root level (like global or local) in which you can put your configurations.
In the above example, the extension was created in the global level.
By default, extensions are disabled, meaning they don’t impact you commands. Try to enable this extension with.
clk extension enable myextension
Enabling extension myextension in profile global
One tricky aspect of extension is that there are two levels to take into consideration:
- the level in which the extension is created, meaning the folders where it is located,
- the level in which the extension is configured, meaning where you tell whether or not it is enabled.
This may look complicated, but you’ll get used to it. Once you master it, you can fulfil several use cases.
Notes linking here
- clk and contextual polymorphism
- clk encourage de scripter par abstraction
- clk extension dependencies
- clk levels provide sensible locations to put configuration
- clk personal feature extension
- clk shared personal extension
- polymorphic command line interface (in clk)
- use clk extension to ease contextual polymorphism