We do have that branch in azure and tests show it can ping it etc

agent-specified

means the node classifier, i.e. the Console, will use the environment that the agent requests. So whatever is in the agent's

puppet.conf

is what will be used for the environment.

puppet.conf does not have any code to explicitly pickup production

Usually it just look at production

The list should show production in its values like it did before but it does not so trying to fix it

one thing to be aware of… the console has a cache as that can be an expensive request if there’s many environments, on the classes tab of the node group detail screen there’s a refresh button

Screenshot 2025-11-13 at 14.37.56.png

I do know but that doesnt fix the issue of production not showing

to narrow things down, what does puppetserver list?

Untitled

did you try running explicitly with production, like

puppet agent --test --environment production

and then see if the next runs without explicit

environment

setting keep using production

Good Morning.. Any ETA on PE 2025.7 , more with respect to the Puppet Agent upgrade to v8.17?

question: is there a way to make

pdk test unit

ALWAYS emit coloured text? if i run it with

| grep

or

| less -R

, the output isn't coloured.

yeah, that’s a pipeline thing, I think. Not Puppet’s fault.

I run into it with other things and just have to live with no output.

i've seen (and written) tools that automatically enable or disable output colouring based on whether STDOUT is a tty or not ... almost always these tools will have options to force colour on, or force colour off. i'm hoping that

pdk

has options like this, and they just aren't documented anywhere (including in the

pdk test unit -h

output).

here’s why I think it’s the pipe… do this:

pdk --help |grep update

it strips the colors

now do this:

pdk --help |grep update --color

grep is the thing stripping colors.

no, grep is adding the colours. if you run

pdk -h

, the word

update

is green. with

pdk -h | grep --color update

, the word

update

is red.

even so, this doesn’t just let the text with its existing colors pass

what you’re saying is “search for <this> and then color it so I can see it”

run

pdk -h | cat

... you'll see what i mean

grep --color

uses

$GREP_COLORS

to highlight matching text, not pass the original colour through the pipeline.

the problem (for me anyway) is that

grep

isn't RECEIVING the colour codes in the first place.

the difference is whether `pdk`'s STDOUT is a TTY or not... if it's not a TTY, the

pdk

command isn't sending the colour codes.

side note ... i had asked (last week maybe?) if there was a way to pre-set the template URL/ref that

pdk new module

uses, so you don't need to remember to include the

--template-url=

and

--template-ref=

options ... turns out the answer is yes:

pdk set config user.module_defaults.template-url git@github.com:USER/REPO
pdk set config user.module_defaults.template-ref main

(obviously the URL format can also be

https://

or

ssh://

, or any other URL scheme for which the machine has a remote helper installed ... like on my workstation i could also use

keybase://

or

foks://

)

You can include the ref in the URL, too.