Skip to content
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

Template Zones #39

Open
ShaneMcC opened this issue Sep 24, 2017 · 5 comments
Open

Template Zones #39

ShaneMcC opened this issue Sep 24, 2017 · 5 comments

Comments

@ShaneMcC
Copy link
Member

It would be nice to be able to create "Template Zones" that can define a bunch of records.

Then provide an "Insert from template" feature to allow inserting these records into a zone.

@ShaneMcC
Copy link
Member Author

(A secondary nicety would be dynamic template zones, so the template zone gets updated and all the records in child zones get updated as well, without needing to worry about re-importing)

@ShaneMcC ShaneMcC transferred this issue from mydnshost/mydnshost-frontend Nov 11, 2018
@ShaneMcC
Copy link
Member Author

My biggest problem with dynamic template zones (or building-block style templates like mydnshost/mydnshost-frontend#38) is how this works with the domain-permissions system (which is pretty funamental to my aims for mydnshost)

eg with:

  • Domain1 (User1 has write, User2 has Read)
  • Domain2 (User1 has write, User2 has none)
  • TemplateA (User1 has write, User2 has write)

If Domain1 or Domain2 uses TemplateA - that gives User2 write access to Domain1 + Domain2 indirectly.

Or:

  • Domain3 (User1 has write, User2 has write)
  • TemplateB (User1 has write, User2 has none)

If Domain3 uses TemplateB - User2 can't see some of the records that get added.

(I'm sure there are other annoying combinations that I've not considered yet)

How do we handle things like this?

@ShaneMcC
Copy link
Member Author

For problem 2:

I guess I could just enforce that anyone who has access to a domain gets read-access to any template that is added to that domain. (This could be enforced by automatically ensuring all users of a domain are automatically added to the template when it was added, and then checking when trying to remove them if that is allowed)

@ShaneMcC
Copy link
Member Author

For problem 1:

I could just show a warning when adding templates that it may allow users to create records in templates that will be copied into the main zone and make it a user-problem to ensure they don't do silly things. (Maybe show a warning if it is actually the case)

@ShaneMcC
Copy link
Member Author

(Maybe. Other thoughts/ideas welcome!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant