Puppet Community

<http://master.eastus.cloudapp.azure.com|master.eastus.cloudapp.azure.com>

I did not see a PuppetDB article in the archives

Because it’s in a draft form sitting right here on my desktop

Thing is, EVERYTHING tends to get in the way.  I should just do a quick check to make sure the AWS interface hasn’t changed, do a full stand-up, then tidy and publish.  Should just take about a day

heyyyyyyyyyy i actually used this to set everything up. I'll head back and read it

I have to point to my own website now.  This used to be in the Puppet Blog, but that all changed after the acquisition.  :slightly_smiling_face:

Back before they started supporting a split-architecture Puppet Community, you used to have to rsync around certs and crl’s, do fancy tricks with server pooling, etc.  It’s *SO* much better today.

yes. At the moment Puppet isnt maintaining/publishing containers

<@U11JXDFJ9> I see what you're saying in your doc.  What should I do if, when standing these compilers up i forgot to add "<http://load.eastus.cloudapp.azure.com|load.eastus.cloudapp.azure.com>" to the list of dns_alt_names, and added it later?

something like this? <https://www.puppet.com/docs/puppet/7/ssl_regenerate_certificates.html#ssl_regenerate_certificates> although it seems to focus on agents and CA

figured it out. Thanks <@U11JXDFJ9> you're amazing!!!! regenerated the certs and all is now well

You'll need to set up some mechanism that notifies Code Manager to run a deployment after code pushes. Continuous Delivery is handling this piece in your other environment.

With just Code Manager, there are a few options. Adding a webhook to BitBucket is probably the simplest:

<https://www.puppet.com/docs/pe/2023.0/code_mgr_webhook.html#triggering_code_manager_with_a_webhook>

Great Thanks a lot....reading links..thanks

I'm getting so rusty that I'm sure it's something obvious, I can't see it

<@U11JDM8UF> What exactly is complaining? Is it Puppet or `puppet-lint`?

Can you share the error message/complaint text.

```Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Class[Profile::Global_db_migrate]: expects a value for parameter 'credentials' at /etc/puppetlabs/code/environments/production/modules/role/manifests/dbmigrate/app.pp:3:3 on node &lt;redacted&gt;```

nvm.  I saw pp.pp, and I thought there was a typo, but that's the `pp` from app

If `$credentials` is required, you should define the parameter as:
```String[1] $credentials,```


And if it's not getting a value, it means the Hiera lookup is not finding anything.

Perhaps because the node running Puppet isn't matching any of the levels in the hierarchy.

so when we make that line look like that, we get the error above.  When we make it look like my top post, it works and finds the hiera value.

If I do `puppet lookup` on that key for that node, it finds it in the correct file

Is there a typo maybe?
Is that text you pasted exactly what it is, or did you type that out by hand?

that's pasted, although I removed the body of the class

so at least I'm not completely misremembering how APL is supposed to work, I guess

I saw that from the top post, and commented that it was redundant, and when they tried it without, it threw the error.  so weird

On line 3 of `role/manifests/dbmigrate/app.pp`, how is the `profile::global_db_migrate` class being decalred?

good question.  I had the same thought.  it's an include, though
```class role::dbmigrate::app {
  include profile::cloud_sql_proxy
  include profile::global_db_migrate
}```

How did you do the `puppet lookup`, and what options did you pass to it to verify that the lookup works?

That error message is telling me that Hiera _can't find_ the key.
So I suspect maybe your manual `puppet lookup` wasn't exactly correct.

Also, where in the hierarchy is that key's value defined? Is it in some low-level common file, or is it higher up in the hierarchy and gated by some fact?

That is to say, what facts and/or variables are used in the hierarchy definition for the layer in which `profile::global_db_migrate::credentials` exists?

Did you do a `puppet lookup --explain ...`?

yeah, I did an explain:
```puppet lookup --node &lt;redacted, but the same as above&gt; --explain profile::global_db_migrate::credentials```

```      Path "/etc/puppetlabs/code/environments/production/hiera/dbmigrate/app.yaml"
        Original path: "%{facts.project}/%{facts.role}.yaml"
        Found key: "profile::global_db_migrate::credentials" value:&lt;redacted&gt;```

Are you running Puppet against the `production` environment?

Ah, yes you are. It's in the error message.

once he's done doing what he's doing, I'm gonna mess around and see if I can figure it out.  I just really thought I was forgetting something dumb

I checked both the potential puppet servers as well, but the dude working on this is also pretty rusty setting up new hosts, so there might be something off

Yeah, the Puppet code looks correct.
And the `puppet lookup --explain` looks good.

At this point, I'd suspect a code deployment problem and/or Puppetservers being out of sync.

so guess what happened when I tried to recreate the problem?

totally worked fine for me when I removed that default.  no clue what was wrong before.

That is redundant, correct. Because Puppet will automatically lookup the `profile::global_db_migrate::credentials` key due to Automatic Parameter Lookup.

On line 3 of `role/manifests/dbmigrate/app.pp
`, how is the `profile::global_db_migrate` class being decalred?

```--explain ALL THE THINGS```
:allthethings:

I started to push our organization :shrug: let's see how far I can get

awesome, thank you! we can do custom solutions for sponsoring if none of the options work for your company. just ping me

Do you receive a receipt when sponsoring?

i got an email, didn't look at it though lol

:coffee: _:teacher:Puppet Forge_ is about to start up in <#CFD8Z9A4T|>

IMG_5061.jpg

Hi Team,

Does puppet agent verion 7.21 supports some specific format of fact file? 

But it should automatically create right format right?

Hello all,
i'm using the foreman + puppet to install and config package, having some problems while deploying chrony:
Class chrony::install is private (file: /etc/puppetlabs/code/environments/production/modules/chrony/manifests/install.pp, line: 5, column: 3)
Looking a that file it has assert_private()
How can i solve this?^