# 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:	HI-23

Status:	suspended

Project:	perforce_software-helix-installer

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2019/08/20 15:08:58

ModifiedBy:	tom_tyler

ModifiedDate:	2020/01/28 09:40:28

OwnedBy:	tom_tyler

Description:
	Add a -no_sudo flag to skip sudo elevation.

DevNotes:
	[2019/08/20 ttyler]: Suspending this job for now due to lack of a
	driving customer, and because of what things will break w/o sudo.
	
	[2020/01/28 ttyler]: Further thought: With systemd baked into
	modern Linux, having sudo for the perforce user is now a hard
	requirement to start/stop the server presently.
	
	It might make sense to have a flag that generates a more narrow
	sudo file rather than open access, e.g. allowing only start/stop
	of p4d/p4broker/p4p services.  Or potentially modifying the sudo
	configuration so that the perforce user can start services without
	requiring sudo.
	
	That said, having full sudo is often required depending on the
	scope of the role of the Perforce Helix administrator, especially
	on dedicated hardware.

Component:	core

Type:	Feature