Can't use parameters in TermGroup Managers and Contributors nodes in pnp provisioning schema
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
Hi all, when using parameters in the Name attribute of the user node, the PNP provision fails. It tries to get the user without expanding the placeholder. I don't know if it is related to the pnp:User node or the TermGroup Managers / Contributors nodes.
<pnp:TermStore>
<pnp:TermGroup Name="{parameter:TaxonomyGroupName}">
<pnp:TermSets>
<pnp:TermSet Name="TestSet">
<pnp:Terms>
<pnp:Term Name="TestTerm"></pnp:Term>
</pnp:Terms>
</pnp:TermSet>
</pnp:TermSets>
<pnp:Contributors>
<pnp:User Name="{parameter:RootSiteOwner}" /> <!-- will fail with "can't find the user {parameter:RootSiteOwner}" -->
</pnp:Contributors>
<pnp:Managers>
<pnp:User Name="{parameter:RootSiteOwner}" /> <!-- will fail with "can't find the user {parameter:RootSiteOwner}"-->
</pnp:Managers>
</pnp:TermGroup>
</pnp:TermStore>
Contributor guide
No contributing guide indexed for this repository
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 with the PnP provisioning engine's handling of TermGroup Managers and Contributors, using the provided TermStore example to trace how the User Name value is resolved. Check whether parameter expansion occurs before the user lookup. Done means parameterized users in both Managers and Contributors resolve successfully instead of producing the placeholder lookup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100