# The form data below was edited by tom_tyler
# Perforce Workshop Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#
#  Status:        Job status; required field.  There is no enforced or
#                 promoted workflow for transition of jobs from one
#                 status to another, just a set of job status values
#                 for users to apply as they see fit.  Possible values:
#
#                 open - Issue is available to be worked on.
#
#                 inprogress - Active development is in progress.
#
#                 blocked - Issue cannot be implemented for some reason.
#
#                 fixed - Fixed, optional status to use before closed.
#                 
#                 closed - Issue has been dealt with definitively.
#
#                 punted - Decision made not to address the issue,
#                    possibly not ever.
#
#                 suspended - Decision made not to address the issue
#                    in the immediate future, but noting that it may
#                    have some merit and may be revisited later.
#
#                 duplicate - Duplicate of another issue that.
#
#                 obsolete - The need behind the request has become
#                    overcome by events.
#
#  Project:       The project this job is for. Required.
#
#  Severity:      [A/B/C] (A is highest)  Required.
#
#  ReportedBy     The user who created the job. Can be changed.
#
#  ReportedDate:  The date the job was created.  Automatic.
#
#  ModifiedBy:    The user who last modified this job. Automatic.
#
#  ModifiedDate:  The date this job was last modified. Automatic.
#
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#
#  Description:   Description of the job.  Required.
#
#  DevNotes:      Developer's comments.  Optional.  Can be used to
#                 explain a status, e.g. for blocked, punted,
#                 obsolete or duplicate jobs.  May also provide
#                 additional information such as the earliest release
#                 in which a bug is known to exist.
#
# Component:      Projects may use this optional field to indicate
#                 which component of the project a givenjob is associated
#                 with.
#
#                 For the SDP, the list of components is defined in:
#                 //guest/perforce_software/sdp/tools/components.txt
#
#  Type:          Type of job [Bug/Feature].  Required.
#
#  Release:       Release in which job is intended to be fixed.

Job:	SDP-532

Status:	open

Project:	perforce-software-sdp

Severity:	B

ReportedBy:	neal_firth

ReportedDate:	2020/04/22 16:38:06

ModifiedBy:	tom_tyler

ModifiedDate:	2021/04/27 11:04:08

OwnedBy:	neal_firth

Description:
	Would like broker config to be a symlink rather than file.
	
	Would like broker config to be a link rather than an actual file
	within init script parameter requirement. If system maintenance
	results in a restart of the host (accidental or otherwise) the
	default broker init will take over and expose the system (real
	world ugly experience because config file wasn't a link). If
	config always referenced a specific config file that was in turn
	a link then there would explicit control over the mode of broker
	operation. Variation would also be obvious from the command line
	by looking at the link. Design thought would be to add
	'setvariant' and 'clearvariant' p4broker init modes that adjusted
	the config link based on a variant parameter. Or maybe just
	'setvariant' with a built-in DEFAULT variant. A specific init
	command seems cleaner than changing the link based on context.

DevNotes:

Component:	init

Type:	Feature