pki.git/base/deploy/src/pkispawn, branch master

Renamed base/deploy to base/server.

2013-04-09T13:40:09+00:00

The base/deploy folder has been renamed to base/server to match the
package name. The pki.conf has been moved into pki-base package.

Ticket #553, #564

Handle the Keyboard interrupt gracefully.

2013-03-26T19:22:47+00:00

Catch the KeyboardInterrupt (Ctrl-C) input during the execution of
pkispawn and pkidestroy and display a proper message to user rather
than a stacktrace.

Ticket #536

Added security domain info validation.

2013-03-07T22:51:32+00:00

The installer script has been modified to validate security domain
info in both interactive and silent installation.

A basic Python API has been added to access the REST interface.

Ticket #473

Added DS info validation.

2013-03-07T22:51:27+00:00

The installer script has been modified to validate DS info in both
interactive and silent installation.

Ticket #472

Added interactive subsystem installation.

2013-02-04T23:48:02+00:00

The pkispawn has been modified such that the configuration file
and subsystem type are optional. The pkidestroy has been modified
such that the instance name and subsystem type are optional.
If any of these options are not specified they will enter an
interactive mode.

Ticket #380

Archiving default deployment configuration.

2012-12-04T20:50:55+00:00

The default deployment configuration has been renamed and moved to
/etc/pki/default.cfg to make it more accessible to users. The pkispawn
has been modified to archive the default deployment configuration
along with the user-provided configuration in the registry. The
pkidestroy will now use both archived configuration files to ensure
proper removal of the subsystem.

Ticket #399

Interpolation correction patch based on review comments

2012-12-04T17:11:53+00:00

Use interpolation to build default parameters

2012-12-04T17:11:36+00:00

This patch replaces the code in pkiparser with defaults that are
built up using ConfigParser interpolation.  The patch gets most
(but not all) default parameters.

Replaced links of scriptlets with lists.

2012-11-30T21:03:27+00:00

Previously the deployment tools used symbolic links to determine the
scriplets to execute and their order. The code has been changed such
that now the scriplets are listed as parameters (spawn_scriplets and
destroy_scriplets) in the configuration file.

Ticket #403

Reorganized sensitive parameters.

2012-11-30T21:02:48+00:00

Previously sensitive parameters are stored in the Sensitive section in
the configuration file, separate from the hierarchical structure used
by non-sensitive parameters. To allow defining multiple subsystems in
a single configuration file the sensitive and non-sensitive parameters
have been reorganized into the same hierarchical structure.

To maintain the security a new meta-parameter has been added to list
all sensitive parameter names. This way the deployment code will know
whether a parameter is sensitive, which then will mask the value before
displaying it to the screen or storing it in a log file.

Ticket #399