dsccommunity / dsccommunity/SharePointDsc
SPServiceAppSecurity: Unable to specify remote farms
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 246
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Details of the scenario you tried and the problem that is occurring
It might not be possible to specify remote farms for this resource. It has not been tested as no environment is available to do so, but based on the implementation details there is no code paths that will work when specifying a remote farm as Member
Verbose logs showing the problem
N/A
Suggested solution to the issue
Implement a way to specify remote farms (Farm Id)
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version of SharePoint that is used (e.g. SharePoint 2016)
SharePoint 2013/SharePoint2016
Version and build of PowerShell the target node is running
5.1
Version of the DSC module that was used ('dev' if using current dev branch)
2.5.0.0 and unreleased version PR #892
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the SPServiceAppSecurity implementation and the changes referenced by PR #892, focusing on how Member is handled. Done means the resource supports specifying a remote farm by Farm Id for SharePoint 2013 and SharePoint 2016; no reproduction configuration or test environment is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100