Skip to content

Commit

Permalink
Release v1.2.2
Browse files Browse the repository at this point in the history
  • Loading branch information
jathanism committed Aug 30, 2017
1 parent fb46a49 commit 9e64f13
Show file tree
Hide file tree
Showing 4 changed files with 41 additions and 13 deletions.
13 changes: 13 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,19 @@ Changelog
Version History
===============

.. _v1.2.2:

1.2.2 (2017-08-30)
------------------

* Support for object-level permissions have been implemented using the
``django-guardian`` plugin. For tree objects (currently ``Interface`` and
``Network`` objects) that can have children and ancestors, the permissions
will be inherited by child nodes *unless a more specific permission has been
set on the child object*.
* Object-level permissions may be managed using the built-in admin dashboard.


.. _v1.2.1:

1.2.1 (2017-08-01)
Expand Down
2 changes: 1 addition & 1 deletion docker/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ RUN pip install -U setuptools

# Try to run this as late as possible for layer caching - this version will be
# updated every update so let the build not take longer than necessary
RUN pip install nsot==1.2.1
RUN pip install nsot==1.2.2
COPY conf /etc/nsot

ENTRYPOINT ["nsot-server", "--config=/etc/nsot/nsot.conf.py"]
Expand Down
37 changes: 26 additions & 11 deletions docs/models.rst
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ All Resource types support set query operations. Set queries are a powerful
part of the data model that allow you to perform complex lookups of objects by
attribute/value pairs.

Set queries can be performed using a simple string-based syntax.
Set queries can be performed using a simple string-based syntax.

The operations are evaluated from left-to-right, where the first character
indicates the set operation:
Expand Down Expand Up @@ -484,17 +484,32 @@ A typical User might look like:
Permissions
===========

Permissions, like other objects, are specific to Sites. There are no
permissions that cross over sites. All objects are readable regardless
of permissions. There is currently only one type of permissions a User
can have in order to make modifications:
By default all new users have superuser (admin) and therefore modifying
permissions is not necessary in default installations.

* admin
Permissions control three basic actions for each object and come in two
flavors: global and object-level.

+ Ability to Update/Delete Site
+ Ability to grant permissions within a site
+ All subsequent permissions
The basic permissions for each object are:

Site creation is open to all users. Upon creating a Site you become
an admin of that Site with full permissions.
* add
* change
* delete

Global Permissions
------------------

If assigning permissions to a user or a group, global permissions can be
assigned to individual resource type, for example "Add Network" or "Change
Device".

Object-level Permissions
------------------------

Permissions can also be assigned to individual objects, for example
``Network('10.10.10.0/24')``. These permissions can be added from the admin
dashboard view for the object.

For tree objects (currently ``Interface`` and ``Network`` objects) that can
have children and ancestors, the permissions will be inherited by child nodes
*unless a more specific permission has been set on the child object*.
2 changes: 1 addition & 1 deletion nsot/version.py
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = '1.2.1'
__version__ = '1.2.2'

0 comments on commit 9e64f13

Please sign in to comment.