What does KT stand for in the Puppet Environment name?
Puppet environment names have the following structure:
KT_ORG_ENV_VIEW_#
where ORG is the organization name, ENV is the lifecycle environment, VIEW is the content view name, and # is an internal sequence number.
What does KT stand for in the Puppet Environment name?
Responses
I am interested to know if anyone is using these generated Puppet Environments in their processes/workflows?
I am defining environments for my agents through automation and haven't found a use case for these Katello/Satellite generated environments. Can anyone link to documentation that incorporates these generated environments into the system lifecycle?
Pixel, this won't answer your question, but I happened across something with the title of "Which repository provides katello-agent and puppet packages for Satellite 6 client systems? ". The "solution" for satellite 6.0.x is https://access.redhat.com/solutions/1184073 and for Satellite 6.1... https://access.redhat.com/solutions/1427513.In satellite 6.1, it says "Users utilizing Red Hat Satellite 6.1 should no
longer be using the 'Red Hat Common' repositories for client libraries including
Puppet, katello-agent and others."
This bit I put here is not to fit as an answer to your question, but might help those with
some isue with katello-agent/puppet package repositories, for satellite 6.0 and 6.1
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
