-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Update license user association from has one to has many #768
Update license user association from has one to has many #768
Conversation
3c8d7e7
to
b759ca1
Compare
567d86d
to
a4b9b76
Compare
acbdde0
to
42fe29d
Compare
a13d73f
to
b4ca925
Compare
47ba74f
to
da06f95
Compare
a537bb1
to
d88c8af
Compare
d88c8af
to
02d5f60
Compare
New plan: with the proof of concept Let's clean up |
3d5aa06
to
d6183bc
Compare
Should a machine belong to an owner? Right now, it doesn't make sense that a machine always belongs to the owner of the license, since in reality, it could belong to any of the license's licensees, not necessarily the license's owner. |
Closes #534.
Prerequisites
user
validation scope to look atLicense#users
.owner
validation scope.License#user
toLicense#owner
.user
relationship toowner
in user serializer.users
relationship to license serializer.data.relationships.owner
todata.relationship.user
for licenses (with updated links).Renamelicense.user.updated
webhook event tolicense.owner.updated
? (Or send both?)Pre-deploy
license.owner.updated
,license.users.attached
,license.users.detached
,machine.owner.updated
event types.license.owner.update
,license.users.attach
,license.users.detach
,machine.owner.update
permissions.Post-deploy
licenses.user_id
tolicenses.owner_id
? (May want to do this during our next maintenance window.)Renamelicense.user.update
permission tolicense.owner.update
?license.owner.update
,license.users.attach
,license.users.detach
,machine.owner.update
permissions to relevant roles.