Plugins built into images and not into UI
- Dominant language
- Python
- Stars
- 9
- Forks
- 41
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
I apologize ahead of time for this being a generic "issue". I tried asking on the forum and got zero response... Credential plugins seem to get zero love in the community. :)
I cannot find any documentation on how these plugins are built and published to the main AWX project & UI. I found where this repo is listed in the requirements_git file, and I can see that they are being pulled into the base image, but the plugins themselves are neither shown in the UI or returned via the API.
Can we get some documentation or at least high level steps on how to test/include these plugins when building awx from devel?
Contributor guide
Research direction
Start by tracing this repository's entry in requirements_git and how the plugins are included in the AWX base image. Check the devel build path and the UI/API behavior described in the issue. Done means documenting how to test and include credential plugins, plus explaining whether and how they should appear in the UI and API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100