Feature #7394

Accept punctuation characters in Puppet environment

Added by Oliver Hookins about 1 year ago. Updated 7 days ago.

Status:Closed Start date:05/04/2011
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:3.0.0
Affected Puppet version:2.6.7 Branch:
Keywords:
Votes: 1

Description

Currently, AFAIK, Puppet environments can only accept upper- and lower-case alnum characters. It sure would be nice if it also accepted some subset of punctuation characters. Most desirable for me are hyphen, underscore and period.

History

Updated by Nigel Kersten about 1 year ago

We do currently accept underscores Oliver, but you’re right, we don’t accept hyphens or periods.

Does supporting underscores give you enough functionality?

Updated by James Turnbull about 1 year ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

Updated by Nigel Kersten about 1 year ago

  • Status changed from Needs Decision to Needs More Information

waiting to see whether the underscore is sufficient for Oliver.

Updated by Oliver Hookins about 1 year ago

Our app names can have underscores in them, but releases usually have hyphens e.g. 2011-R1.

It is good to know that underscores are accepted as that will immediately reduce some of my hacks but hyphens would be great. Periods would be the icing on the cake.

Updated by Nigel Kersten about 1 year ago

  • Status changed from Needs More Information to Accepted
  • Assignee deleted (Nigel Kersten)
  • Target version set to 3.x

Updated by Andrew Forgue 12 months ago

I would love to see periods in environments so I could namespace the dozen or so environments we have going at a time.

Updated by Nigel Kersten 8 months ago

  • Status changed from Accepted to Needs More Information
  • Assignee set to Andrew Forgue

Can someone outline the advantages of periods and hyphens over underscores for namespacing?

Is there an associated attribute that it makes sense to be able to use for environments? Are people wanting use cases like mapping subdomains to environments and wanting to use the subdomain directly as the environment?

Assigning to Andrew for an answer as you replied last :)

Updated by Nigel Kersten 4 months ago

Looking for more info here still.

We’ve generally had a lot of issues with hyphen support due to Ruby not supporting them in symbol names, thus the hesitance to add hyphens.

Updated by Andrew Forgue 4 months ago

  • Assignee deleted (Andrew Forgue)

I honestly don’t remember what I was doing that required those things in environment names, but I don’t need them now. Probably can close this unless you guys want do to it anyway.

Updated by Oliver Hookins 4 months ago

It’s a similar situation for me. We’ve automated the environment manipulation part so far out of normal users' reach that they never interact with environments directly anyway, so the character set is not such a limitation anymore.

I’d be happy for this to stay open but I’ve got many other features/bugs that I actually care about so I’m not sad about losing one of my babies so to speak ;)

Updated by Daniel Pittman 3 months ago

  • Status changed from Needs More Information to Closed

Thanks, everyone. We will consider this again if new information comes along, but we are generally reducing places those punctuation characters can be used, and they add ambiguity that we would rather avoid…

Updated by Daniel Pittman 14 days ago

  • Target version changed from 3.x to 3.0.0

Updated by Erik Dalén 7 days ago

We would use it to map environments to git branches that typically contain slashes, at the moment we use a wrapper script that mangles any punctuation to underscores. That works quite well though, but if you consider adding more characters slashes would be nice for git branch mapping.

Also available in: Atom PDF