pnp
💡 [Feature]: Add more manage capabilities for Tenant Wide extensions
🎯 Aim of the feature
Currently, the extension just shows the tenant-wide extensions on our SPO tenant. The idea is to add some management capabilities to it. Some ideas from the top of my head are:
- Remove
- Enable/Disable
📷 Images (if possible) with expected result
🤔 Additional remarks or comments
Possible things we could allow to modify https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/basics/tenant-wide-deployment-extensions
@Saurabh7019, @nicodecleyre I would appreciate your feed on this feature 🙏. What do you think?
sounds great; it will only make the tool richer. I will be happy to implement it when it's open.
sounds great; it will only make the tool richer. I will be happy to implement it when it's open.
Thanks for the feed. What do you think if the open points? Like the ability to modify list template or web template? The problem here is that those actions would not make sense for every extension type. Also we could allow to modify the order/priority. This number specifies the order in which the extensions are loaded on a page. What do you think?
Users can update Title, Properties, Web template, List template, Sequence, etc. from editing the item in the Tenant Wide Extensions list, and I think we should also support it from the SPFx TK without worrying if updates have any effect on the extension or not.
I would think of actions like -
- Rename
- Update Properties
- Disable
- Enable
- Update Sequence
- Update Host Properties
too much? maybe, we can start with the ones you initially mentioned.
Users can update Title, Properties, Web template, List template, Sequence, etc. from editing the item in the Tenant Wide Extensions list, and I think we should also support it from the SPFx TK without worrying if updates have any effect on the extension or not.
I would think of actions like -
- Rename
- Update Properties
- Disable
- Enable
- Update Sequence
- Update Host Properties
too much? maybe, we can start with the ones you initially mentioned.
I like your proposal. Let's do it like this. Let's leave the scope of this issue as is and do a follow up issue with the additional stuff you mentioned 👍
@nicodecleyre what do you think?
Users can update Title, Properties, Web template, List template, Sequence, etc. from editing the item in the Tenant Wide Extensions list, and I think we should also support it from the SPFx TK without worrying if updates have any effect on the extension or not. I would think of actions like -
- Rename
- Update Properties
- Disable
- Enable
- Update Sequence
- Update Host Properties
too much? maybe, we can start with the ones you initially mentioned.
I like your proposal. Let's do it like this. Let's leave the scope of this issue as is and do a follow up issue with the additional stuff you mentioned 👍
@nicodecleyre what do you think?
Sounds like a solid base to me 💪 I was thinking about another action, namly clone where we can clone an existing tenant wide extension but with other properties.
What do you think about that action?
@nicodecleyre sounds interesting. But wouldn't we need to like create a totally new sppkg package which should be redeployed with a new GUID in order to avoid some conflicts? I never had such a case to have the exactly same SPFx extension added to the tenant wide extension list twice but with different properties 🤔
@nicodecleyre sounds interesting. But wouldn't we need to like create a totally new sppkg package which should be redeployed with a new GUID in order to avoid some conflicts? I never had such a case to have the exactly same SPFx extension added to the tenant wide extension list twice but with different properties 🤔
Yeah, you're right.. Forget what i said 😄
ok, thanks @Saurabh7019 and @nicodecleyre for helping me on this idea. I will open up this issue with the basic set of actions we could allow for the tenant wide extensions and start working on a follow up issue with based on this comment https://github.com/pnp/vscode-viva/issues/435#issuecomment-2772673170