https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • t
    You are right. there is no ‘in’ matcher. But: you can specify the fact array using index numbers to check for content. but that requires you to either specify multiple indexes or you must know in which index the value is located. (in pe console: 
    array_fact[0] = 'value'
    )
  • b
    morning people o/ https://github.com/puppetlabs/puppet-classify is a gem to interact with the classifier. Is there a similar project with API bindings for the PE orchestrator? I didn't find a matching one on rubygems.org
  • b
    morning people o/ https://github.com/puppetlabs/puppet-classify is a gem to interact with the classifier. Is there a similar project with API bindings for the PE orchestrator? I didn't find a matching one on rubygems.org
  • b
  • s
    This message was deleted.
    d
    b
    • 3
    • 11
  • b
    someone knows the difference betweehn the 
    /command/plan_run
    and 
    /command/plan_start
    API endpoints in the orchestrator: https://www.puppet.com/docs/pe/2019.8/orchestrator_api_commands_endpoint.html#orchestrator_api_post_command_plan_run 
    plan_run
    is documented, 
    plan_start
    isn't. but 
    plan_start
    is used in the Ruby lib: https://github.com/puppetlabs/orchestrator_client-ruby/blob/master/lib/orchestrator_client/command.rb#L14
  • b
    also I think the naming of plans vs jobs vs commands vs plan-jobs is.. challenging 😄
    sadpanda 1
  • d
    i see some reference in our internal slack which refer to it as the "old api"
  • s
    This message was deleted.
    b
    t
    • 3
    • 6
  • b
    puppet_enterprise::profile::orchestrator::job_prune_threshold
  • s
    This message was deleted.
    m
    b
    n
    • 4
    • 14
  • s
    This message was deleted.
    s
    b
    • 3
    • 20
  • d
    Posting to main channel so these updates to download pages are visible: I wanted to check the list of updates they have made make sense as well as the further comments. " I have a few updates related to this one.
    it looks like a 2023.0.0 release page was not created. That is why its not showing up in the Releases listing page https://www.puppet.com/releases. I do see that this page https://www.puppet.com/downloads/puppet-enterprise has the 2023.0.0 downloads on it, I have created a 2023.0.0 release page https://www.puppet.com/releases/2023.0.0. I also also added in a CTA in the header of the Releases page with a link to this downloads page https://www.puppet.com/downloads/puppet-enterprise
    " It was also highlighted " The PE releases (redirect for pe_repo) has been updated to include the repo tarballs (under "agent repos", towards the bottom of the page) The instructions for airgapped are still there (albeit not obvious) eg: install *nix agents with pe package management https://www.puppet.com/docs/pe/2023.0/installing_nix_agents.html#install_nix_agents_pe_package_management
    Before you begin
    [...]
    If the agent node does not have internet access, download the appropriate agent tarball, and copy the agent tarball to this location on the primary server:
    /opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-<AGENT_VERSION>
    There is similar note under before you begin for windows agents (it does use backslashes for the path even though the location you're copying it to is a *nix server as primary can't be windows but ... separate doc ticket for another time) ("
  • s
    This message was deleted.
    this 2
    d
    b
    s
    • 4
    • 3
  • b
    message has been deleted
  • b
    @steveax another PE console idea: visualize puppet plans. I've a a few plans that call a huge amount of other plans and tasks. Displaying that as a graph after a plan is done would help a lot in big setups. could even be added to bolt
  • m
    Does anyone know hickups that might occur converting a centos 8.5 PE Primary to Rhel?
  • s
    This message was deleted.
    v
    m
    e
    • 4
    • 10
  • m
    a licencefile is usually in with the .key extension?
  • s
    This message was deleted.
    m
    r
    • 3
    • 6
  • m
    in other instance simply making a new branch solved the issue as there was something jgit didnt like in the git history
  • m
    Iv never seen just one cause, but its usually around something structural in the repo itself and how it interacts with the jgit client puppet uses
  • m
    Iv never seen just one cause, but its usually around something structural in the module repo or control repo itself and how it interacts with the jgit client puppet uses
  • k
    Does anything need to be "turned on" within PE in order to utilize sub profiles directory structure? In one of my Roles include the following "path" :
    Copy code
    profile::linux::base
    I understand that the actual base.pp file would live in: site-modules/profile/linux/manifests/base.pp However when I run puppet agent I get a 500 error:
    Copy code
    Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not find class ::profile::linux::base for ash-qa2-docker99 (file: /etc/puppetlabs/code/environments/production/site-modules/role/manifests/dockerhost.pp, line: 4, column: 3) on node ash-qa2-docker99
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
  • v
    that's incorrect path
  • v
    proper will be module/manifests/subclass/subsubclass.pp
  • v
    so, 
    profile/manifests/linux/base.pp
  • v
    site-modules is something site specific
  • v
    we just use 
    modules
  • k
    ahhhhh
1...383940...73Latest