Icinga / Icinga/icinga-powershell-framework
[feature request] Support for 3rd party plugins in Repository
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 87
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I would like to install plugins via icinga-repositories that are not written as powershell-plugins.
There should be a new icinga-component type for this. This could define the installation location, support config/doku and enable versioning.
Examples are .exe plugins, perl/python whatever scripts, config snippets(yml,ini,json,etc.)
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
No files, tests, or entry points are named. Start by defining the proposed icinga-component type and its relationship to icinga-repositories, including installation locations, configuration and documentation support, and versioning for executable plugins, scripts, and config snippets; done means these requirements have an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100