Deploy to Ansible Galaxy about ansible-elasticsearch

[gingerwizard]

@strootman @patcon i'll look at this tomorrow. It hasn't been on the priority list. We need to discuss as it seems to require giving access to the Elastic repo.

[pmoust]

On the other hand, nothing prevents us from creating a bot user as an external collaborator with access only to elastic/ansible-elasticsearch and provide public_repo to its token.
/cc @dliappis @elasticdog

[gingerwizard]

Added https://galaxy.ansible.com/elastic/elasticsearch/

[gingerwizard]

@strootman We're assessing but don't currently see any reason why not.

[bbaassssiiee]

Elastic, you only give read-access to your repo. The advantage of Galaxy is that we can all install a stable version of the vendor supported role instead of browsing through hundreds of homegrown roles by third parties where they don't keep up to their maintenance burden, like @strootman.

[strootman]

For those who may have looked at the role and found it wasn't up to date on Ansible galaxy, it is now up to date with the current master.

[bbaassssiiee]

That is not the same thing, it is a fork, but the maintainer is not Elastic. Elastic pushed to GitHub, they can also tag the release and publish on Galaxy to do a proper job.

[mariussturm]

Using this role as a dependency is also only possible when there is an official Elastic role on Galaxy. We can't use a fork for that.

[patcon]

bump?

[strootman]

FYI, I've forked this repo and imported to ansible galaxy;

https://galaxy.ansible.com/CyVerse-Ansible/elasticsearch/

No promises on keeping it up to date ;)

[gingerwizard]

When i tried this it needed readonly access to the whole elastic repo. Given this contains commercial code i need @elasticdog @dliappis input prior to proceeding. cc @kevinkluge

[pmoust]

AFAIK Github does not provide a much needed granular control over oauth scopes per repo.
repo and public_repo provide read-only and ready-write access across the whole org as @gingerwizard mentions above. Ref: https://developer.github.com/v3/oauth/#scopes

[elasticdog]

I spoke with @gingerwizard and agree that it makes sense to have a dedicated machine user to provide access for this use case.

[bbaassssiiee]

🦄

[mariussturm]

The Galaxy app only requests access to public repositories, permissions look like:

• Access public repositories
• Read org and team membership
• Access user email addresses (read-only)

[jesusch]

any news on this?

[strootman]

@jesusch I've been pushing a fork of this repo to ansible galaxy, and I just updated it.
https://galaxy.ansible.com/CyVerse-Ansible/elasticsearch/

[strootman]

@bbaassssiiee @mariussturm then don't use it.
I put it up there just in case it fit someone's needs. It fits mine.
I also don't keep up on it, and only updated it today since I saw that @jesusch posted a *bump* on this thread.

I would prefer that Elastic support it officially, but they don't yet.

I'm honestly glad to see so many people actively monitoring this issue.
I hope it illustrates that there is a real customer need for having this role published to ansible galaxy.

Particularly for its use as a dependency, as @mariussturm suggests 👍