Puppet Community

but that should not be affecting my current issue of not being able to specify an environment at the command line, despite me creating the agent-specified env group, does it?

Or should I make that agent-specified env group a child of the `Production` group, since that's the one that contains the other environments?

sorta depends on the rules that are set up too

This might help: <https://www.puppet.com/docs/pe/2021.7/grouping_and_classifying_nodes.html#environment_vs_classification_group>

Would PE LTS get support of Amazon Linux 2023 by any chance ?

Or we need to hack the installer script locally?

Given the relationship with Fedora 34-36 and CentOS 9 Stream, I'd guess _maybe_ the next LTS release could be massaged to run on AL2023 but I'd be (happily) surprised if it is listed as officially supported.

considering AL will now have a 2 years release schedule, same as LTS, it will always lag behind :disappointed:

maybe joining this mailling list here?
<https://groups.google.com/g/puppet-announce>

i see this quite a lot in 2021.7.2 in the logs while code deployments happen. is this already addressed?
```/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/rugged-0.27.7/lib/rugged/repository.rb:258: warning: Using the last argument as keyword parameters is deprecated```

<@U11MKJ5D4> <https://tickets.puppetlabs.com/browse/ENTERPRISE-1461>

obviually this has been reported already by you. i need a what-has-tim-reported-now-again-rss feed :smile:

there's this confluence page with all issues and you can probable get a feed from it with changes :smile:

now that jira is split into on-premise and cloud, not all my tickets are associated with the same account :disappointed:

I think PE2021 is for sure. Some 2023 might be based on 8

2023 will flip to Puppet 8. That was announced today in the roadshow meeting

good to know - we have an evaluation setup for 2023 but probably won't be moving anytime soon (we just moved off PE 2019 to 2021 in February, because, well, procrastination)

PE2021 is an LTS release and feature locked.  It will not go to P8.

PE2023 is our Feature release and will get new features and functionality (including P8) during it's lifecycle.  PE2023 should get P8 in 2H23.

Yup, 2023 will switch to using Puppet 8 before it hits the LTS period of its lifespan.

Oh, I missed that in the docs - I’ll see about getting that fixed!

Thank you, Todd, for this feedback, and thank you, Steve, for opening a Jira ticket.

Just this morning, I was in a meeting where we discussed the "Environment-based testing" topic. I need to do more research, but we are considering extensive revision of this topic based on the feedback received.

I have the following agent-specified node groups:

Is there a way - in my puppet code - to determine to which of these groups a node is part of?

Nodes get added to these automatically based on their host names

is there some fact i can access that may have this information?

in general, your code should be environment neutral. what is your use case?

Well - in this case, depending on which of these tiers its in, I'd like to set a specific activation key that is application-tier specific.

in other words - if its a member of the `acp_app_tier` - it should get a key called `acpkey`

Seems like something you could add as a module parameter and set in the PE console for each node classification.