Resolved 6464-Windows-Services-Start-binPath-Args-issue #6465
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request check list
Affected functionality
Instead of using non-persistent Start Parameters in windows services as we do using code below.
We can use just create service command that will create the service with all the arguments. The arguments are persistent and the service can start automatically.
sc.exe create spire-server binpath= "c:\spire\bin\spire-server.exe run -config c:\spire\conf\server\server.conf"Description of change
In service_windows enterypoint, I have used os.Args that will accept Arguments form binPath. The code has condition to check if os.Args are valid if not then it will check Start Parameters Args if they are also invalid then it will throw error same as before.
Which issue this PR fixes
fixes #6464