Galaxy Release 1.1.1

October 30, 2015 by Chris Houseknecht

galaxy-blog-header.png

 We’re back again with a quick update to Galaxy. In the last release we did some cool things to make searching roles much easier. This release is a mini release focused on fixing a few bugs and adding minor enhancements we couldn’t squeeze into the last cycle.

Galaxy issues are tracked publicly at https://github.com/ansible/galaxy-issues. Here are the issues addressed in release 1.1.1:

#88 Role Data Should Show Last Modified Instead of Created Date

#86 `ansible-galaxy -r roles.txt` - Incorrect Example

#84 README.md Fails to Render When it Contains a Variable String Like

#82 "Sign in" Option Should Appear on Home Page Header

#81 Better Filter for RHEL/Centos -> EL in Platform Search

#53 Adding a Role Called "Ansible" Results in Un-named Role

#14 Add Galaxy support for Debian Jessie

#9 Periods in Role Names Cause Installs to Fail

Fuzzy Searching

As part of fixing issue #81, Better Filter for RHEL/Centos -> EL in Platform Search, we changed the way the new role filtering works. A lot of times you know what you’re looking for, and don’t want to wait for autocomplete suggestions. For example, you might be looking for a Platform value of ‘centos’. Typing ‘centos’ into the search box produces a suggestion list containing ‘EL’ for Enterprise Linux. With the new change you no longer need to wait for the autocomplete list to learn that ‘centos’ maps to ‘EL’. Instead, just type in ‘centos’, hit the return key, and all roles with a Platform of ‘EL’ appear.

This change applies to Tags and Authors as well. Instead of needing to search for exact values Galaxy now performs a ‘fuzzy’ search. For example, type in ‘dev’ for the Tag value, hit the return key, and all roles with a Tag equal to or similar to ‘dev’ are returned with the most relevant listed first.

Roles Named Ansible

Issue #53 highlighted a problem encountered by several authors attempting to create a role with the name ‘ansible’. A few succeeded, but many attempts resulted in a role being created with no name at all. This has now been fixed so that a role can be created with the name ‘ansible’ or ‘Ansible’ without doing anything tricky.

By default Galaxy uses the Github repository name to determine the role name. You can override this by providing an alternate name when importing the role. During import Galaxy removes the strings ‘ansible’ and ‘ansible-role’ from the beginning of the name. However, it now allows a name consisting of only ‘ansible’ or ‘Ansible’.

What this all means is that there are a couple different ways to create a role named ‘ansible’. A Github repository named ‘ansible’ or ‘ansible-role-ansible’ will result in a role named ‘ansible’. Or, simply providing an alternate name value of ‘ansible’ will work.

What’s Next?

As always we’re continuing to iterate on Galaxy. In release 1.2 we will be looking at how to bring Github organizations into Galaxy. Adding a download count to roles is on the list. And, we’ll start work on role testing. Keep an eye on the progress of release 1.2 by watching Galaxy Issues.

 

Share:

Topics:
Ansible Galaxy


 

Chris Houseknecht

Chris is the Principal Engineer at Ansible by Red Hat. Starting as employee number five, Chris keeps watch over Ansible Docker modules, maintains Ansible Galaxy and is the lead Engineer for Ansible Container. When he’s not working he spends his time cooking, walking his dogs or outside on his mountain bike or motorcycle. He can be found on twitter at @chouseknecht.


rss-icon  RSS Feed

Ansible Tower by Red Hat
Ansible In-Depth Whitepaper
ansiblefest brooklyn 2016
Learn About Ansible Tower