Right now the hosting-import assumes the name of the drush rc file, which is stripped of everything but alpha numeric. Where as in the front-end you can name it what ever you want. It would be nice to be able to name it something a little more human readable.

Comments

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Note how this is a similar problem to #1003536: allow arguments to hosting-task @site task.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Title: name parameters on hosting-import drush call » Configurable context/alias names

I don't think we can name the drushrc whatever we want in the frontend.. in both cases the context name is stripped down.

Renaming the ticket to what I think is the request

mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented

My use case for this, working up a continuous integration setup similar to your zero touch article, mig5. One of the things the script does is import the newly built platform into aegir. Platforms imported this way end up with very unfriendly names. Would be better if we could specify the platform's display name as part of the hosting import task.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

mrfelton: can't you specify a more friendly name for the platform when you save its alias, before running hosting-import?

What I mean to say is, hosting-import uses the name of the alias as the platform name, so if you name the alias something friendly, it's ok.

But now I realise you're probably wanting to save a platform name with, say, whitespace, which obviously won't work since that name also is used to create the alias file, and the @alias name itself... So yeah perhaps we need a separate --name flag for such a thing.

mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented

@mig5 exactly. We call our platforms something along the lines of example_7_x__20120403__120 - it lets us identify it as the 7.x branch of the example platform built on 03/04/2012 Jenkins build number 120... But a more readable string, with whitespace, hyphens, periods and other readable characters would be a lot better IMO.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

In #2031397: Configurable context/alias names we are thinking about making it possible to *add* an extra alias to the existing one, would that answer your request?

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Title: Configurable context/alias names » Configurable node title for hosting import
Version: 6.x-0.4-alpha3 » 7.x-3.x-dev
Issue summary: View changes

I'm pretty sure we're talking about adding a field to contexts that will be used as the node title during hosting-import. So, essentially the reverse of the other issue.

I've updated the title to reflect this, but correct me if I'm wrong. Also, new features go in the 7.x-3.x branch.