Table of Contents
Advertisement
Chapter 2
Creating Provisioning Scripts
Some_Entry
Multiple plain text files can be spliced together to generate the source for the final binary CFG file. This
is accomplished using the import directive at the start of a new line followed by one or more spaces and
the file name to splice into the stream of parameter-value pairs. File splicing can be nested several files
deep.
For example, the file base.txt contains the following:
Param1 "base value 1" ;
Param2 "base value 2" ;
The file spa1234.txt contains the following lines:
import base.txt
Param1 "new value overrides base" ;
Param7 "particular value 7" ;
When compiled, spa1234.txt becomes:
Param1 "base value 1" ;
Param2 "base value 2" ;
Param1 "new value overrides base" ;
Param7 "particular value 7" ;
Comments
During development and scripting, it is often convenient to temporarily disable a provisioning parameter
by entering a # character at the start of the parameter value. This effectively comments-out the remaining
text in that parameter.
For example, a Profile_Rule with the value
empty Profile_Rule. The # character comment-mechanism applies to the Profile_Rule*, Upgrade_Rule,
and Resync_Trigger_* parameters.
Macro Expansion
Several provisioning parameters undergo macro expansion internally prior to being evaluated. This
preevaluation step provides greater flexibility controlling the resync and upgrade activities of the SPA.
The parameter groups which undergo macro expansion before evaluation are as follows:
•
•
•
•
•
Under certain conditions, some general purpose parameters (GPP_*) also undergo macro expansion, as
explicitly indicated in the Optional Resync Arguments section.
Version 3.0
!
Resync_Trigger_*
Profile_Rule*
Log_Resync_*
Upgrade_Rule
Log_Upgrade_*
;
# user read-write, leaves value unchanged
"# http://192.168.1.200/sample.cfg"
Proprietary Plain-Text Configuration File
is equivalent to an
Linksys SPA Provisioning Guide
2-9
Hide quick links:
Advertisement
Table of Contents
