Greg,

How's it coming with github organization support? I own the github 
organization "griidc", under which I have created several ansible role 
repos. I would like those repos to be listed in galaxy as griidc.rolename. 
I cannot create a galaxy account for griidc because it is a github 
organization, not an account (and galaxy now only accepts github for new 
accounts). It looks like, currently, ansible namespaces are still tied to 
github usernames (I couldn't find any way to change or create a new galaxy 
namespace). Will there be a way to create an ansible namespace for griidc?

Thanks,
James

On Tuesday, November 24, 2015 at 12:25:20 PM UTC-6, Greg DeKoenigsberg 
wrote:
>
> On Tue, Nov 24, 2015 at 1:01 PM, Tim Rupp <[email protected] 
> <javascript:>> wrote: 
> > Hi all, 
> > 
> > I'm part of an organization on github that wants to publish a role to 
> galaxy 
> > as that organization. My account in linked in galaxy as the account that 
> is 
> > part of the organization and when I specify the "username" in the galaxy 
> > field, it continues to use my personal account instead of the 
> organization 
> > account. 
> > 
> > I'm told that the organization itself doesn't have a "user + password" 
> combo 
> > anymore. Can anyone provide info on how to publish content on galaxy as 
> the 
> > organization so that it doesn't show up on galaxy as my personal 
> account? Is 
> > this possible? 
>
> Tim, 
>
> Right now there's no way to do it; we don't map well to Github 
> organizations, only Github user accounts. 
>
> Stay tuned, though; we're currently evaluating some very big changes 
> about how Galaxy interacts with Github. 
>
> The basic idea: no more Galaxy user accounts, and anyone can upload 
> any Github repo (though of course only the people who own the repo can 
> actually change the contents.)  Artificial distinctions between Galaxy 
> and Github namespaces will go away. Also makes galaxy cli 
> functionality for batch role management easier. 
>
> We should have a demo to show in the coming weeks. 
>
> --g 
>
> > Thanks, 
> > tim 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Ansible Project" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/ansible-project/ad39b67c-08b2-4f33-b188-f21a1eadb8f0%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Greg DeKoenigsberg 
> Ansible Community Guy 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/8a5646a8-e30d-4148-bef1-13069dddc681%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to