Download the PHP package dmstr/yii2-rbac-migration without Composer
On this page you can find all versions of the php package dmstr/yii2-rbac-migration. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dmstr/yii2-rbac-migration
More information about dmstr/yii2-rbac-migration
Files in dmstr/yii2-rbac-migration
Package yii2-rbac-migration
Short Description _____
License BSD-3-Clause
Homepage https://www.dmstr.io/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package yii2-rbac-migration
Yii RBAC Migration
This migration allows one to define the desired 'state' of rbac item structure.
A multidimensional array is used to define how the desired item structure should look after the migration.
Following the style of puppet config, the main attribute defining the desired or
expected state of an item is the ensure parameter.
Since this type of migration change security related data, it is recommended to rather define a defensive configuration.
Installation
Example usage
config params per privilege item
- default params for all items are defined via
protected $_defaultFlagsStructarray - default params can be defined/overridden per migration instance via
public $defaultFlags - params which are set directly at the items have the highest priority
defined params are merged per item.
| param | value | required | default | description |
|---|---|---|---|---|
| name | string | yes | null | rbac item name |
| type | Item::TYPE_ROLE or Item::TYPE_PERMISSION | no | Item::TYPE_PERMISSION | rbac item type |
| ensure | see ensure flags | no | self::NEW | ensure state of the item after and before migration |
| replace | boolean | no | false | weather item will be updated if exists |
| rule | array | no | none | array of name, class properties that will be used as rule for this item |
| description | string | no | none | description property of the item |
valid flags for ensure param
| flag | desc |
|---|---|
| self::NEW | new item will be created, error if already exists |
| self::MUST_EXIST | item must exist, error if not |
| self::PRESENT | ensure item exists, if replace == true update/replace, otherwise leave as is |
| self::ABSENT | if item extists item will be removed. Handle with care! |
hints for self::ABSENT
- If defined as item param, the item will be removed regardless of its position.
- So if you define
ensure => self::ABSENTin child items, NOT only the child relation but the item will be removed! - if auth items are defined in DB and the auth tables has FK with cascade, child relations for this item may be deleted by the db.
hints for rules
- if defined rules are assigned to item "by name".
- if not exists it will be created with the given class property.
- if rule with given name already exists and
replaceis set totrue, rule will be updated, otherwise existing rule will be used.
deprecated item params
the params _exists and _force are deprecated but still valid and will be replaced with new params scheme
| deprecated param | converted to |
|---|---|
| _exists | 'ensure' => self::MUST_EXIST |
| _force | 'ensure' => self::PRESENT, 'replace' => true |
shortcut syntax for mass assignments
to be able to quickly define mass assignments a special shortcut syntax where item is just a string can be used. The string will be set as item['name'] property, all other params are used from (defined) defaults.
Example:
safeDown()
These auth migrations can not be reverted.
Built by dmstr
