The most important feature missing in Semaphore

[fiftin]

What's missing in Semaphore?

[MrChausson]

Task templates scheduling, this would be great to have.
It should display some warnings when modifying a task template / inventory which is already scheduled.

[fiftin]

Thank you. It will be implemented soon, just after vault/password feature.

[fiftin]

Task templates scheduling added:
https://github.com/ansible-semaphore/semaphore/releases/tag/v2.7.14

[scomcd]

We currently query the DB to generate a report showing scheduled tasks and their run times, but if possible, it would be great to have a view created within the GUI showing the Tasks that have been scheduled and their scheduled run times including date & time for next run etc

In the Task Templates view, it would be helpful to have an option that forces the alias string for each task to be unique. We use a sequenced alpha-numeric string as the alias for many of our tasks but the system currently allows duplicates.

[eisemakr]

hmm an improved user guide, would be great. There are many entries missing and in the wiki here many things are only very briefly described. I know this is an open source project :) and everyone like more to code than document but this would make it much more useful to others.

[fiftin]

Thank you, I agree, I working on docs. You can help the project by following it on Twitter and StackShare.

[Freebase394]

Many Thanks! @fiftin and everyone !
This softwer its amazing! I'm testing it right now and i'm loving it.
I come here from Ansible AWX/AWX operator nightmare installations!

[steadfasterX]

from my point of view the following is required for serious usage of semaphore in companies but also for me as private person: #891

[jdhayes]

I agree with @steadfasterX, for enterprise users they will probably need better defined roles and perhaps LDAP authentication.

However, a more pressing feature for me is the API and how it could be extended.
I would really like to see an implementation of the "--limit" within the API so that the ansible run can be run exclusively on the calling host.

I am already running this in production with the following fork:
https://github.com/jdhayes/semaphore

I have also made a new pull request:
#811

[ansibleguy]

For limit see: Feature - Limit as own Field

[Freebase394]

Could someone add simple tooltip on app to show how to add and execute simple commands to Inventory machines like "apt-get update" or "apt-get upgrade -y" please

[s3lph]

Report when Ansible exits with changes!

This is a feature I'm currently missing from both AWX and Semaphore: Both only report whether a task succeeded or failed. Neither report whether a playbook run resulted in any changes. AWX has had a corresponding issue for some years now, but without any activity AFAICT.

Implementation of such a feature doesn't sound too trivial. I currently see two ways how this can be achieved:

1. As suggested in the corresponding AWX issue: parsing the play recap section of the output.
2. Injecting a callback plugin into each run which would return the play recap in a form readable by Semaphore.

Unfortunately, neither of those sounds like a robust solution, as one involves parsing output intended for humans, and the other could interfere with other custom plugins.

[flyingfishflash]

A server->project level configuration property defining the length of time to keep the various types of generated data (activity/task execution history and output).

[derpedda]

Live-Tasklog would be amazing, reloading to see if the task succeeded is pretty painful (websockets are an option to achieve that)

[steadfasterX]

yea. it is working fine on the dashboard at least but not in the task template view

[allebone]

Direct Netbox Support for Inventory and Access to Rendered Content.

Lots of shops out there working on IaC are using Netbox as the single source of truth for their network configurations. I am working to solidify that concept on my team, but with Semaphore as the Executor of that Vision.

Having a direct and better connection to Netbox would allow regional/site specific semaphore installations to run against only their devices, and allow the non-coding crowd to focus on making Netbox look "true." Netbox could then run Webhooks targeted at Sempahore to execute a Task via the API, closing the loop.

I can elaborate more, but it seems like a Win-Win for Netbox and Semaphore.
Semaphore + Netbox.pdf

[jdhayes]

Dynamic inventory is already an Ansible plugin away for Netbox source of truth.
I am using a custom script currently, but may change over to a more fully functional alternative.

https://docs.ansible.com/ansible/latest/collections/netbox/netbox/nb_inventory_inventory.html

[allebone]

Oh for sure, I was just thinking for the bigger audience, adding a direct to Netbox Inventory configuration to the Sempahore GUI could eliminate a lot of the requirements.yml confusion. Plus to be honest, as a member of the Network Engineering crowd...it might spur a few to use Source of Truth in their life. :)

[fredix]

Hi all !
for me the biggest feature missing are the workflows : https://docs.ansible.com/ansible-tower/latest/html/userguide/workflows.html
Thanks for your excellent application.