https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • b
    but I can probably hack the http client to use different cert/privkey for the different puppetservers 🤔
  • v
    But client doesn't request catalog, the tool requests it on client behalf ?
  • v
    that's why you need adjust auth.conf to use catalog_diff
  • b
  • b
  • b
    If I've different CAs I also have different certs for the catalog_diff and I currently cannot configure that
  • v
    hmm, why won't you copy CA to puppet7 server for catalog evaluation?
  • v
    you can always start with new CA when you are ready for a new infra
  • b
    yeah I'm considering it. at the moment I've three CAs. the new compiler and two existing setups. I could setup a forth compiler and have one for each existing infra
  • b
    or just run catalog-diff from two users 🤷
  • v
    beware that catalog_diff will fail to find a difference if providers will change behavior. noop is the only way to catch those, unfortunately
    👍 1
  • b
    yeah 😞
  • b
    or actual beaker tests
  • v
    https://github.com/voxpupuli/puppet-jenkins/pull/1041 I got it to pass locally with CentOS 8 (technically not in the supported OS list), also ran some of the plugin tests individually
  • v
    let's see if CI agrees
  • v
    ah nicr
  • n
    Copy code
    ## Deprecated modules
NAME                  | DEPRECATED_AT            
----------------------|--------------------------
camptocamp-postfix    | 2021-08-26 05:20:19      
npwalker-pe_databases | 2020-03-24 14:47:09      
puppet-staging        | 2018-12-18 11:11:29      
razorsedge-snmp       | 2018-12-10 16:00:19      
rmueller-cron         | 2018-03-02 09:55:58      
vshn-gitlab           | 2018-02-08 09:25:47
  • d
  • n
    When looking at deprecated modules is there a way to automatically determine what replaced it? Some of these modules were moved to vox while others were not. I would like to be able to either query the forge or the metadata to determine this information.
  • b
    in an ideal world, the forge people would react quicker than within 6 months after we raise deprecation tickets and the problem would dissappear 🙂
  • n
    Yes, but shouldn’t this be the module owner’s decision?
  • s
    This message was deleted.
    b
    n
    +2
    • 5
    • 22
  • b
    sometimes the original owners are hard to reach. and they can only mark a module as deprecated. if the module is/was approved, they cannot move that badge to use. A ticket needs to be raised for this
  • v
    the forge API does have a field
  • v
  • v
    ewoud: yes, but only the owner of a module or the Forge team can mark it
  • v
    correct, but not sure how you'd do it otherwise
  • v
    indeed
  • v
    that won't work, it would allow takeovers
  • v
    bastelfreak: damn, threading makes these fun to follow, haha
1...313233...648Latest