Puppet Community

Perfect and thank you! I guess I'll open a support case to have the docs fixed then :slightly_smiling_face:

I think the current plan makes sense and also the xml idea. I made similar stuff in the past from a physical network point of view

and I think it would make sense to merge your plan into the pe_status_check module?

yeah eventually, need something stable before i put it in there since status check is in the product right now

do you know anything opensource that can draw from xml?

i figure outputting to a format another tool can use to draw this would be a good start

what about the dot language? puppet uses that as well for graphs

and there are libs available to write dot language and also to render it into svg

could work, as what we are talking about here is basically a relational table schema

i wonder how it would handle 1 to many data points or would i have to render a diagram for each service type

the way i see it, its gonna output a list of nodes, and a list of services,  and then have a table to plot the services on the node host, as well as a coomunication line of the services on other hosts

it feels more like a psuedeo relational database table stucture

would be nice to use the vox pupuli module for tables to generate humand readable output and maybe dot for graphs or json and people can then convert it on their own

only issue with using modules is it prevents me from shipping with PE, i have to use native functions only

mhm every month I am searching for that git repo

<https://github.com/voxpupuli/puppet-format|https://github.com/voxpupuli/puppet-format>

PE could vendor it? it already vendors other modules (and damn old forks of modules...)

yeah, thats been noted :slightly_smiling_face:

This would actually be a start i could probably list each host node with a service, and if its a client of an upstream service list the upstream hostname and a status for the link

ideally i could draw a network map, but getting a table based structure is just about spending the time determining which components i want to interrogate, and doing them one by one

thinking about it, a functional network map like <https://github.com/puppetlabs/puppetlabs-peadm/blob/main/documentation/images/PE_Large_Architecture_no_DR.png|https://github.com/puppetlabs/puppetlabs-peadm/blob/main/documentation/images/PE_Large_Architecture_no_DR.png> would be cool

but displaying the real architecture with real configured ports/ips

everbody hates to draw <http://draw.io|draw.io> diagrams in confluence that are outdated after a month

it would be more helpful if we could autogenerate it

thats what i have on my whiteboard, the easy but time consuming part is getting that data, the part i have no idea about is how to draw it like that, im hoping a tool exists and i can just output a format that it can read

<https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/> for something simple maybe

or something like this <http://go.drawthe.net/>

this one seems easy enough <https://mermaid.js.org/syntax/c4c.html>

the benefit about the dot syntax would be that there are existing libs to use. it's human- and machine-readable and it would be consistent with what puppet agent uses

I think it would be useful, but would likely need a fair amount of my side project time,

pdk question - not sure which channel is best to ask.  I have an older module created here, when I do "pdk validate", it says "using Puppet 6.29.0".  pdk update makes no changes, and convert says nothing to change.  what sets this?

There should be a "pdk-version" entry in metadata.json for the PDK version and in the "requirements" array a dictionary entry for the Puppet version in the same file.

yea, the version was &lt; 7.0.0.  would've expected the pdk update to change that

I think `pdk update` just updates the `pdk-version` in `metadata.json` and syncs in any changes from the `template-url` and `template-ref`.

<@UCBN6H9N3> pdk checks the latest supported major puppet version in your metdata.json

if you don't allow puppet 7, pdk will default to test with puppet 6

<@U1PC2RAH0> agreed on that.  just.  <@U11MDJNGZ> good point, I think my templates need to be updated

created custom about 2 yrs ago as we were creating a lot of boilerplate app modules

most three common errors I saw: code-manager was still deploying the env, you deployed env A but selected emv B in the PE console, there is a syntax error in the plan

I think I figured it out. I use get_target and it's not supported from orchestrator. Although it's funny that it works from bolt command line. I'm hoping that gets resolved eventually as the plan I wrote is to migrate nodes to different PE silos.

ah yeah a few functions are missing in the PE implementation

You also have to add permissions for whichever role to view the bolt jobs (admin can see them all of course)

Yeah, the permissions are fine. I have unsupported functions in my plan. I'm pretty sure it's the get_target function stopping it from showing.

<https://www.puppet.com/docs/pe/2021.7/plans_limitations.html#unavailable-plan-language-functions>

<https://www.puppet.com/docs/pe/2023.2/plans_limitations.html>

I’d have a look at the puppetserver and orchestration-services logs too

`ds_pw_obfuscated` is indeed a field that the API returns, so the provider would need to be updated to accept that, or at least follow Postel's Law by tolerating arbitrary extra fields in the API output and just checking that required fields are present.

I think `ds_pw_obfuscated` has been around for a long long time too. Although, 2019 is 4 years ago now... :what_year_is_it:

yeah. I didn't see it on PE 2019. the provider uses the resources api, that was probably updated as well from 2019-&gt;2021

don't know if the rbac api changed or if a newer resource api version just doesn't like the missing field

you want to update it or you want to know the current state?

its been escalated to a high priority ticket but there is no further update yet. I will highlight this on the internal channels

I opened a sev2 ticket, my infra is totally dead :disappointed:

That's disappointing let me see what I can find out

I have unlinked  /etc/puppetlabs/puppetserver/code (I use versioned deploy) and puppetservers came online, so it's not as bad now

I think it could be to this  process. kill doesn't get rid of it and I am hesitant to use kill -9
```pe-pupp+ 2468844       1  0 10:12 ?        00:00:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/bin/r10k deploy --config /opt/puppetlabs/server/data/code-manager/r10k.yaml --verbose warn --cachedir /opt/puppetlabs/server/data/code-manager/worker-caches/deploy-pool-1-2 environment production --modules --incremental```

you could always use signal 15 which is a bit nicer, and will give you dditional output if STDOUT was respected….

Just to confirm is the workaround using unlinking still having impact?

unlinking helped to bring puppetservers up

but puppet code deploy still fails. and I think that process might to blame

Right im just going to highlight  this is not a everything working workaround if code deploy is still failing / running that long. I'm not sure they are clear on that

```# strace -p 2468844
strace: Process 2468844 attached
futex(0x9981e0, FUTEX_WAIT_PRIVATE, 0, NULL```

It’s giving me empty string for command_op variable here in my code.. <@U2S1MUUQ7> 

Hmm, why not  to use already existing facts?

and you should use `Facter.debug` instead of puts

<@U2S1MUUQ7> what’s the existing fact name?

```# facter networking.network
10.135.147.0```

I’m looking for just the primary network adapter network info. 

I see…thanks for helping me <@U2S1MUUQ7> . I believe this should work for me. Any reason why the above code is failing to parse the same ?

What is the process to update the location for your puppet repo on the puppet master
 Is this something you can do from the UI directly?

```puppet_enterprise::master::code_manager::sources:
  unix:
    remote: "<mailto:git@gitlab.example.com|git@gitlab.example.com>:it/puppet/puppet-control.git"```

you can set that in console too, but hiera is easier

<@U2S1MUUQ7> What If I'm using a repo in Azure DevOps and I'd like to read using a PAT like I do in Jenkins