siw36 / awx-judge Goto Github PK

If the launch of a job (AWX API call) fails, the judge (admin) should be able to manually trigger a retry.

Create a background job to launch approved requests.
The background job should launch requests periodically for now.
The launched job should get watched and the request state should get updated accordingly.

Should at first be able to talk to Azure.
The user accounts should get created after login.
The admin account then can assign permissions to the imported identities.

If a user leaves the project or something similar, he needs to be able to assign the ownership of his requests to a group or a user. So that his team can go back and check what requests he made.

Special case: a playbooks logs its execution in a audit log and needs requester and approver for that.
In this case the approver could add extra vars to a request when approving it.

For example when creating users in a environment that requires to log user create/disable operations.

Build a basic function to reload data every x seconds.
Later: use MongoDB operations log and websockets to refresh data.

Add the option to add a certificate to mux.
This is used when no SSL reverse proxy e.g. OCP router or nginx ingress controller is available.

All operations should generate a message and change the timestamps in requests.

Download all icons (links are stored in DB) when the container starts.
This allows for a deployment without a PV and ensures that all icons are present when starting a new container with existing DB data.

Add description and screenshots as well as how to use.

To enable to run multiple replicas of awx.judge, its needed to store user sessions in DB.

Add an email connector to allow sending updated to requests by email.

Represent the current state on master.

Make it possible for users to add a slack notification channel (channel or PM).
This option should only be available when the administrator has set up a Slack webhook integration.
Also make it configurable on what events a notification should be sent.

When using an external identity provider (OIDC), the received user data should get imported.
Those users should be able get put into groups by the admin.

Some API endpoints like judge or settings should only be accessible by members of the judge/admin group.

Use MongoDB operations log to detect changes on requests and publish them through websockets.

Create a modal template for error messages.
Whenever a API call fails, this modal should show up and inform the client about the issue instead of failing silently.

Create a two stage Docker file and build the image on Dockerhub as well as Quay.
Add the information about pre build images to the readme.