chronograf/roles/roles.go

package roles

type contextKey string

// ContextKey is the key used to specify the
// role via context
const ContextKey = contextKey("role")

// Chronograf User Roles
const (
	MemberRoleName   = "member"
	ViewerRoleName   = "viewer"
	EditorRoleName   = "editor"
	AdminRoleName    = "admin"
	SuperAdminStatus = "superadmin"

	// Indicatior that the server should retrieve the default role for the organization.
	WildcardRoleName = "*"
)
Add roles implementation of sources store Minimal test coverage of Update/Delete/Add methods was done since they do not involve any filtering. The filtering for them should have happened at the API level. 2017-11-03 19:32:59 +00:00			`package roles`

			`type contextKey string`

			`// ContextKey is the key used to specify the`
			`// role via context`
			`const ContextKey = contextKey("role")`

Move user roles and role names to roles package 2017-11-03 20:32:05 +00:00			`// Chronograf User Roles`
			`const (`
Change SuperAdminRoleName to SuperAdminStatus SuperAdmin is not a role type, but it a status of a user that is tangentially related to a users role in an organization. This renames the variable to reflect that difference. 2017-11-07 18:59:51 +00:00			`MemberRoleName = "member"`
			`ViewerRoleName = "viewer"`
			`EditorRoleName = "editor"`
			`AdminRoleName = "admin"`
			`SuperAdminStatus = "superadmin"`
Add wildcard role and validate users roles in CRUD The server may now specify a '*' to indicate that the server should retrieve the organizations default role and assign it to the user. 2018-01-12 17:27:55 +00:00
			`// Indicatior that the server should retrieve the default role for the organization.`
			`WildcardRoleName = "*"`
Move user roles and role names to roles package 2017-11-03 20:32:05 +00:00			`)`