-
Notifications
You must be signed in to change notification settings - Fork 0
Introduce namespaces for memberships. #132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
c02760b to
10a34a7
Compare
|
I need to provide more tests for this. |
|
So, I tested this out in multiple places now. First, there are some fresh unit tests for this functionality. Second, I built the existing repositories that use memberships (metal-apiserver and metalstack.cloud api-server) with this pull request and ensured that all tests are passing. Third, I started this PR in the mini-lab and run it along with the metal-apiserver + the metalstack.cloud api-server. I ensured project invitations are now namespaced and that both servers do not see each other's memberships. The projects and tenants can be seen in both APIs of course by design. Here are some extracts: |
* Introduce namespaces for memberships. (#132) * Merge main into connect branch.
Description
Closes #130.