Scope

Frontend (User Interface)

Description

As described in #30 the current data-fetching is far from being perfect.
It does not make sense to have the data fetched if AW is in the background/on an inactive tab.
We could pause the fetching until it has become active again.
See: https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API

Scope

Unknown

Description

I'm an anxiously awaiting your ansible role to cleanly install ag-webui. I'd expect this to be a low priority.

Off to do my first install. Expect more "Issues"!

Side bar; probably due to UBO medium mode and/or user.js on firefox, the checkboxes for Docs and Ansible Docs are not not clickable.

Versions

latest

Scope

Backend (API)

Issue

In case of dynamic inventories or if inventory was configured in ansible.cfg

Scope

Frontend (User Interface)

Description

Sometimes users want/need to executes jobs with some override or a job is always meant to be ran with some given variables (pe. create user X with privilege Y on server Z)

Scope

Frontend (User Interface)

Description

To optimize that view - as it is and will be the most used form in the app

The job screen could be limited to those two fields (playbook/inventory) only with an expander (similar to the "show logs" button?) to reveal the remaining fields.

The schedule-enabled flag is ignored if no schedule is supplied - so that one should be fine in my opinion. Maybe it could also be hidden if no schedule was supplied.

Versions

0.0.19

Scope

Service (Job Scheduling, Job Preparation)

Issue

When sending emails we see: django.template.exceptions.TemplateDoesNotExist: email/alert.txt
This might be because the extension is not distributed - see pyproject.toml

After manually adding the email.txt file to the templates/email directory - it works.

Versions

0.0.16

Scope

Database

Issue

The execution command-field is limited to 1000 characters - this limit could be exceeded by some environments. I see 500-700 chars on some commands.

Versions

0.0.19

Scope

Service (Job Scheduling, Job Preparation)

Issue

Even if the HOSTNAMES setting is set (and PROXY is true) - the links target localhost

Versions

0.0.19

Scope

Service (Job Scheduling, Job Preparation)

Issue

Need to be inline styles: https://stackoverflow.com/questions/35481108/styles-not-working-in-gmail

Scope

Frontend (User Interface)

Description

You can change your own password using the System - Admin page if you are marked as staff.
But not every user is.
There should be a System - Password UI or something like that

Versions

0.0.18

Scope

Frontend (User Interface)

Issue

The way the log-polling/-filtering is done will not work for logs that are older. As the N (unfiltered) entries polled may not include any of the job we filter on

Scope

Backend (API)

Description

Currently we fetch all the data-entries of the current view every refresh-interval (1 sec).
We then check if the data has changed using JS and update the table-rows in that case.

It would be nicer to only fetch the changed datasets. That way we could save on transferred data.
This would mean we will have to pre-filter the data on the backend and implement web-sockets

This is not really an issue for now - but I dislike the current handling as it is somewhat unclean.

Versions

latest

Scope

Backend (API)

Issue

Since implementing the repository functionality we randomly see OperationalError: database is locked errors occurring.
It looks like some write operation locks the database for multiple seconds.
SQLite only supports one write-operation at a time. This is a known limitation.
We should not run into that limitation for some time. The writes we perform are not data-intensive and should easily be done in < 0.1s

Scope

Unknown

Description

Implement Alerting

Versions

0.0.19

Scope

Service (Job Scheduling, Job Preparation)

Issue

If you want to use a mailserver without authentication (p.e. local postfix) the alert will fail with error SMTP AUTH extension not supported by server

Versions

0.12

Scope

Ansible (Job Execution)

Issue

The command was not found or was not executable: ansible-playbook.

Versions

Ansible Web-UI latest
Django 4.2.10
Django Rest-Framework 3.14.0
Gunicorn 21.2.0
Ansible Core ansible [core 2.15.9]
Ansible Runner 2.3.5

Scope

Ansible (Job Execution)

Issue

The target server logs: sshd: Invalid user ansible-webui
It seems the ansible_user variable is not set/used in a consistent manner.
If I create credentials - they work for a few runs. But they stop working after some time.

As a workaround I added -e ansible_user=<USER> as 'Commandline Arguments' of the job.

Also:
It seems if I do not set a specific become-user it defaults to the connect-user - which is not the expected/default behavior: (should be root)
-u <USER> --become-user <USER>
See: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_privilege_escalation.html#become-directives

Versions

0.0.15

Scope

Backend (API)

Issue

Something about the timezone handling is buggy.
If one supplies the AW_TIMEZONE env-var (CET in my test-case) - it will break the request handling.
Probably because it is referenced in the settings.py of django

Versions

Ansible Web-UI latest
Django 4.2.10
Django Rest-Framework 3.14.0
Gunicorn 21.2.0
Ansible Core ansible [core 2.15.9]
Ansible Runner 2.3.5

Scope

Backend (API)

Issue

Manager users marked as staff are able to change permissions they that limit their own access.
They are able to add permissions to grant themselves higher privileges

Versions

0.0.15

Scope

Service (Job Scheduling, Job Preparation)

Issue

The git cloning is not using the configured known_hosts file.
The Git Override Initialize-Command should be documented with some examples.

Got error: 'Cloning into '/tmp/ansible-webui/repositories/TEST'...
Host key verification failed.
fatal: Could not read from remote repository.

Versions

0.0.21

Scope

Backend (API)

Issue

It seems the request class is not linked:
https://github.com/ansibleguy/webui/blob/latest/src%2Fansibleguy-webui%2Faw%2Fapi_endpoints%2Fjob.py#L309

Scope

Frontend (User Interface)

Description

Sort by next run time or alphabetically via name

Scope

Frontend (User Interface)

Description

If no execution prompts are configured, it would make sense to show some common used ones by default.

All optional:

• Limit
• Check mode
• Diff mode
• Tags

Also: add all supported options for the execution-prompts to the UI and/or docs.

Versions

Scope

Unknown

Issue

It might not be a problem depending on the security model but it can in theory allow someone to gain more access than they should have.

See: GHSA-4839-8mxx-4xr9

Scope

Backend

Description

We could add a system setting that globally enables task profiling - could be nice to have.
https://docs.ansible.com/ansible/latest/collections/ansible/posix/profile_tasks_callback.html

Versions

0.0.16

Scope

Frontend (User Interface)

Issue

If one opens multiple logs one after another - they get concatted/merged some times.

Versions

0.0.18 (PIP install)

Scope

Database

Issue

It shows the error sqlite3.DatabaseError: database disk image is malformed before the upgrade starts.
After deleting aw.db-shm and aw.db-wal it works without issues.

Scope

Frontend (User Interface)

Description

We currently have no way of knowing how long an execution has taken.
Maybe add the finish time and duration to the log UI

Versions

Ansible Web-UI latest
Django 4.2.10
Django Rest-Framework 3.14.0
Gunicorn 21.2.0
Ansible Core ansible [core 2.15.9]
Ansible Runner 2.3.5

Scope

Ansible (Job Execution)

Issue

Ansible config:

DIFF_ALWAYS	False	default
DIFF_CONTEXT	3	default

If I enable diff-mode for a job - the -D/-diff flag is not added

Scope

Frontend (User Interface)

Description

When you are troubleshooting some job-setting issue, it would be nice to save on the 'Job - Manage' step

Versions

0.0.18

Scope

Frontend (User Interface)

Issue

The job execution overview is empty (seen on demo)

Scope

Frontend (User Interface)

Description

Would be a common use-case and nice-to-have

Versions

0.0.13

Scope

Database

Issue

I've seen that the Upgrade from 0.0.12 to 0.0.13 failed because the DB schema migration was not executed. It was a PIP-install. A docker install worked without any issues.

Scope

Service (Job Scheduling, Job Preparation)

Description

It might be good to allow and document the usage of GitHub private repositories.
The can be cloned like so: https://${TOKEN}:@github.com/${REPO}
The current implementation needs user & password to be set: https://github.com/ansibleguy/webui/blob/latest/src/ansibleguy-webui/aw/execute/repository.py#L210

Note - currently we might also have issues with the @ inside the uri

Scope

Frontend (User Interface)

Description

The fields list available files but you cannot select them (you either have to type them in or cut/paste)

Versions

latest

Scope

Backend (API)

Issue

Report.pdf

Scope

Frontend (User Interface)

Description

It would be nice if the currently running job would be auto-openend (follow/live view) on the log view

Scope

Unknown

Description

It would be nice to have a job-retry setting.
If the job execution fails because of environmental errors (timeout, network, ...) it could be re-ran automatically.
Default may be 0 - no retries

Versions

latest

Scope

Frontend (User Interface)

Issue

Not able to provide multiple playbooks/inventory files because of browsing functionality.

Scope

Unknown

Description

I have not installed the new ansibleguy-webui, but I've been following progress. I was also following the lack of progress on Semaphore. Thank you for your efforts on this. The demo site is down right now, but I'm planning to install.

Now onto my feature request, I would like native support for SSL certificates, particularly those from Lets Encrypt, but specific support is not essential.

A similar request fell on tone deaf ears in Semaphore. Hoping it evolves here. I don't use containers.

Thanks for the consideration. No scope fits this request, so leaving it Unknown.

Versions

0.12

Scope

Backend (API)

Issue

The manager permissions are a little unintuitive.
P.e. usere in 'Jobs Managers' can create jobs, but not edit them afterwards without an additional permission.
Not even 'Permission Managers' can do so - even though they can just add a permission for themselves to allow it.

I can't think of a situation where a 'Job Manager' should not be allowed to edit/delete a job

Scope

Service (Job Scheduling, Job Preparation)

Description

Would be nice to have the /ui/jobs/log?job=<JOB> link in the alert mails for easy access

Versions

0.12

Scope

Frontend (User Interface)

Issue

It seems the log-view page refreshes in the background, resetting the text the user marked (p.e. to copy an error)

Scope

Frontend (User Interface)

Description

It would be nice if we could choose the user- or global-credentials to use in the execution prompts as an alternative to the 'credential category'

Versions

0.0.16

Scope

Frontend (User Interface)

Issue

The schedule/cron is not very useful on the mobile UI. The next-run might be nicer to have