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

Add restrictions on system stacks based on roles #4807

Closed
sshipway opened this issue May 16, 2016 · 2 comments
Closed

Add restrictions on system stacks based on roles #4807

sshipway opened this issue May 16, 2016 · 2 comments
Labels
area/access-control kind/enhancement Issues that improve or augment existing functionality status/autoclosed

Comments

@sshipway
Copy link

Rancher Version: 1.1.0-dev1

It should be made possible to move a stack between the Normal and System pages.

This function should probably be available to Owners and possibly Members only - but not Restricted Members. Maybe an additional menu item in the Stack menu under 'Edit'?

System stacks should also be protected in some way, EG make them read-only for Restricted Members

@deniseschannon
Copy link

Requesting the ability to make a stack into a system stack is a duplicate of this request.

#3577

But making system stacks protected/restricted access is a different enhancement.

@deniseschannon deniseschannon added kind/enhancement Issues that improve or augment existing functionality area/accessibility labels May 17, 2016
@deniseschannon deniseschannon changed the title Move stacks between normal and system pages Add restrictions on system stacks based on roles May 17, 2016
@will-chan will-chan modified the milestone: Unscheduled Oct 8, 2016
@deniseschannon
Copy link

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/access-control kind/enhancement Issues that improve or augment existing functionality status/autoclosed
Projects
None yet
Development

No branches or pull requests

3 participants