Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

Add option to softwarechannel_setorgaccess for protected sharing of channels #311

Closed

Conversation

photoninger
Copy link

Working with multiple organisations which do not share all channels with each other it is convenient to extend the softwarechannel_[s|g]etorgaccess commands:
I added the option --protected to enable channel sharing only for the given organisations to software_channelsetorgaccess.
software_channelgetorgaccess now reports for protected channels for all trusted organisations if they are enabled or disabled.
And I added software_channel[s|g]etorgaccesstree to work with whole channel trees. Most of the time you want to have the same sharing options on the whole channel tree of a base channel.

I could not figure out why rel-eng/packages/.readme was changed...

channels.

Use -p ORG one or more times to share the channel only with ORG.
Added also two new commands to work with base channel and it's child
channels at once:
softwarechannel_setorgaccesstree
softwarechannel_getorgaccesstree
@jdobes
Copy link
Member

jdobes commented Nov 4, 2015

Hello, I marked 2 lines, build failed because of them. Please look at them.

What's the point of "I dont know what i am doing." commit? :-)

corrected copy/paste error, it has to be
self.help_softwarechannel_setorgaccesstree() within
do_softwarechannel_setorgaccesstree.
@photoninger
Copy link
Author

@jdobes in line 1605 I used do_softwarechannel_setorgaccess as template, there we have also two times "if not len(args)":
The first time args contains all arguments, the second time args only contains the remaining args (channel names) after extracting the options.
So if you call do_softwarechannel_setorgaccess without any arguments the first one will be used, but if you call do_softwarechannel_setorgaccess only with options but without any channel names the second one will be used.
Perhaps the first one can be deleted.

@photoninger
Copy link
Author

@jdobes the "I dont know what i am doing." commit was because git did not allow me to do "git rebase upstream/master" because of unstaged changes in rel-eng/packages/.readme. I did not touch this file and a "git checkout -- rel-eng/packages/.readme" did also not revert the changes.

@tlestach
Copy link
Member

tlestach commented Nov 5, 2015

@jdobes, if you'd accept the PR, please add the bug number 1277994 to the commit messages. Thank you.

@jdobes
Copy link
Member

jdobes commented Mar 24, 2016

It does what it says, merging as one commit - 95dd667 . Thanks.

@jdobes jdobes closed this Mar 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants