Add keycloak tests
Reference Issues or PRs
Competes and fixes #3156
What does this implement/fix?
Put a x in the boxes that apply
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds a feature)
- [ ] Breaking change (fix or feature that would cause existing features not to work as expected)
- [ ] Documentation Update
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no API changes)
- [ ] Build related changes
- [ ] Other (please describe):
Documentation
- [ ] For new features or enhancements, a corresponding PR has been opened in the documentation repository (if applicable)
- Link to docs PR:
Testing
- [ ] Did you test the pull request locally?
- [ ] Did you add new tests?
How to test this PR?
Any other comments?
@viniciusdc @dcmcand It looks like I misinterpreted the green check mark to mean these tests passed in the CI. They are passing locally.
Once the "Await Workloads" test is fixed on the main branch I'll pull that into this branch. Then the CI running these in the following "Deployment Pytests" will run and I can confirm things are green
Thanks, @tylerpotts. I am currently looking into the issue with await_workloads and hope to get it passing in a few minutes.
The CI test is now fixed, small misjudgment on my part
@tylerpotts can you look into the failing tests here so I can approve?
@dcmcand There was a missing expired GPG key in one of the providers. I updated it on this branch and the tests are passing now
@tylerpotts is checking this locally to make sure migration will work out, will hold off on merging this one until then
@viniciusdc Let's hold off on merging this until #3179 is merged. Some of the APIs for keycloak have been updated in v26 and these full tests won't pass until the upgrade in #3179 is complete