| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
* Revive the logstash container for testing
* yamllint
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Sequentiallize auth config removal migrations
- Remove references to third party auth
- update license files
- lint fix
- Remove unneeded docs
- Remove unreferenced file
- Remove social auth references from docs
- Remove rest of sso dir
- Remove references to third part auth in docs
- Removed screenshots of UI listing removed settings
- Remove AuthView references
- Remove unused imports
...
Co-Authored-By: jessicamack <21223244+jessicamack@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
| |
* remove saml
* remove license file and management command
* update requirements, add migrations
* remove unused imports
|
|
|
|
|
|
|
| |
* remove oidc
* remove test fields, linting fix
* merge commit
|
|
|
| |
remove keycloak
|
|
|
|
|
| |
Remove TACACS+ authentication from AWX.
Co-authored-by: Hao Liu <44379968+TheRealHaoLiu@users.noreply.github.com>
|
|
|
| |
Remove LDAP authentication from AWX
|
| |
|
|
|
| |
Remove OpenSSL pin
|
|
|
|
| |
Middleware is from django_ansible_base
|
|
|
|
|
|
| |
* Remove source code for old UI
* Rename ui-next to ui
* Remove license scan for javascript dependencies
|
|
|
| |
update editable deps docs
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change django url dispatcher to serve up ui_next files instead of old ui files
Old UI will not be served with this change
Github CI still runs old ui tests (to be removed in another PR)
Remove the Github workflows that build old UI
---------
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Replaced all references of downstream docs to upstream docs.
* Update README.md
Co-authored-by: Don Naro <dnaro@redhat.com>
* Update README.md.j2
Co-authored-by: Don Naro <dnaro@redhat.com>
* Update README.md.j2
Co-authored-by: Don Naro <dnaro@redhat.com>
* Incorpor'd review feedback from @oraNod and @samccann
* Updated with agreed link (for now) until further change is needed.
---------
Co-authored-by: Don Naro <dnaro@redhat.com>
|
|
|
|
|
|
|
| |
Fix depends_on for awx devel...
when editable dependencies is on
bug introduced by https://github.com/ansible/awx/pull/15386
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Links are use to indicate network connectivity and optionally provide alias
it is not needed for communication since all the container are on the awx network
in the prometheus container case since awx_ container now have valid hostname it's no longer required (also i think the link is missing a `-` anyway...)
links also implicitly imply dependency between services in this i see awx container depends on redis and postgres so i switch to depends_on to retain that
Making this change to be podman compatible
because i get
```
Error response from daemon: bad parameter: link is not supported
```
|
|
|
|
|
|
|
| |
(#15367)
* Update all references to towerhost to platformhost
* Run prettier on failing ui files
|
|
|
|
|
|
|
|
| |
Fix docker build warning
Fix
```
WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 8)
```
|
|
|
|
|
|
|
|
| |
Script was falsely identifying cross-linked
parents. It needs to check if parent roles if
content type is Team and role_field is
member_role OR admin_role.
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
|
| |
|
|
|
|
| |
when doing the final reset of Role.implicit_parents.
|
|
|
|
| |
to trigger the implicit parent not being in the parents and ancestors lists.
|
| |
|
| |
|
| |
|
|
|
|
| |
Since we use it twice, the second time to get the id field of each.
|
| |
|
| |
|
|
|
|
|
| |
Some relationships known to be handled by the special mapping sql file
were being caught as false positives.
|
|
|
|
|
| |
Also, make use of up-front defined arrays of the tables involved, for
ease of editing in the future.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
it wound up being unworkable, and I think ultimately we only need to
check the immediate parentage of each role.
|
|
|
|
|
| |
I think that rebuild_role_ancestor_list() will then correctly update
all of the affected Role.ancestors.
|
| |
|
|
|
|
|
| |
since the foreign keys to the roles from the resources can make us go
wrong almost immediately.
|
|
|
|
| |
The results in my test now look correct.
|
|
|
|
|
| |
This version, however, has false positives because Roles become
children of Team.member_role when a Role is granted to a Team.
|
|
|
|
| |
Checking if parents and implicit_parents are consistent with ancestors.
|
|
|
|
|
|
|
| |
This is actually happening for one customer, though it seems like it
shouldn't be if the foreign key constraint is set back up properly.
In order to recreate it, I had to add the constraint back with 'NOT
VALID' added on to prevent the check.
|
| |
|
|
|
|
| |
Doing the entire graph is too much on any system with real amounts of Roles.
|
|
|
|
| |
Apparently this has happened to a customer, per Nate Becker.
|
|
|
|
| |
of the Role relationships.
|
| |
|
|
|
|
| |
The underlying role should be re-linked, instead of treated as orphaned.
|
| |
|