This is what is used for gitlab and i wonder what the type needs to be if the repo is in azure

@Raj Parpani sounds your a record isn't visible to azure. I'm not at my computer at the moment. Is that dns record queryable from azure. If it's internal only have you got an express route or VPN setup?

The other thing you will need to ensure is that your exposing that address and port to azure in your firewall or it won't connect either

This message was deleted.

☕ 🧑‍🏫Puppet Forge is about to start up in #CFD8Z9A4T

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

fry dancing 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

This message was deleted.

This message was deleted.

The Puppet Learning VM is a fond memory of most long term Puppet users. It was often one of the first interactions with Puppet and after some inevitable fumbling with VirtualBox or corporate laptop issues gave a fun and focused way to learn Puppet via the various quests. As technology has moved on and public cloud made provisioning even easier Puppet practice labs using instruqt is now well established and available seamlessly via your browsers from https://training.puppet.com/ Therefore the repositories related to the Puppet learning VM have been put into the toy chest. https://github.com/puppetlabs/puppet-quest-guide https://github.com/puppetlabs/quest https://github.com/puppetlabs/pltraining-learning https://github.com/puppetlabs/pltraining-bootstrap If any community member/group wishes to adopt these project they can get in contact. As we say a fond farewell to the learning VM, you can find out more about the practice labs which are free and accessible at any time. https://www.puppet.com/blog/puppet-practice-labs https://instruqt.com/blog/frictionless-hands-on-customer-education https://support.puppet.com/hc/en-us/articles/4404442556567-Puppet-Practice-Labs-Free-browser-based-hands-on-learning

Hi all! I'm having a problem with custom resources, using the low-level method, in which the

insync?

and, consequently, the setter functions are not called for properties set to

false

by the user. I reproduced in all Puppet versions I could install - 5 to 8 - and several distro/version combinations. Have anyone else seen this? Could it be an intended behaviour? Test type:

Puppet::Type.newtype(:setter_call) do
  newparam(:title, namevar: true) do
    desc 'Resource title'
  end
  newparam(:previous_state) do
    desc 'Test property previous state'
  end
  newproperty(:desired_state) do
    desc 'Test property desired state'
    def insync?(is)
      Puppet.warning("[Type 'insync?' function] - previous: \"#{is}\" - desired: \"#{should}\"")
      is == should
    end
  end
end

Test provider:

Puppet::Type.type(:setter_call).provide(:setter_call) do
  def send_log(function, previous, desired)
    Puppet.warning("[#{function}] previous: \"#{previous}\" - desired: \"#{desired}\"")
  end
  def desired_state
    send_log('Getter', resource[:previous_state], resource[:desired_state])
    resource[:previous_state]
  end
  def desired_state=(_)
    send_log('Setter', resource[:previous_state], resource[:desired_state])
  end
end

Found out this behaviour is documented in class Puppet::Property method `safe_insync?`:

class Puppet::Property < Puppet::Parameter
  ...
  # @note If the wanted value _(should)_ is not defined or is set to a non-true value then this is
  #   a state that can not be fixed and the property is reported to be in sync.
  def safe_insync?(is)
    # If there is no @should value, consider the property to be in sync.
    return true unless @should
    ...
    insync?(is)
  end
  ...
end

So, if

@should

is undefined,

nil

or

false

, the method returns

true

, no matter the sync status (except that, in my tests,

nil

did not trigger this). I wonder if we could use

return true unless defined? @should

instead. Dunno if

@should

gets defined even if the user doesn't set the property. Thoughts? As far as my code is concerned, I'll switch to the more "Puppety"

:absent

instead of

false

. With some regret of not doing it earlier...

Pls ignore the "nil did not trigger" part. I used

nil

instead of

undef

in Puppet, so I got "nil" string. Fixing the Puppet part got the normal behaviour: no

insync?

call for

false

nor for

nil

. Plus, class Puppet::Transaction::ResourceHarness method

sync_if_needed

doesn't call

Puppet::Property.safe_insync?

if the property's user specified value is

nil

. Is that intended? In the case user specified

false

, is it intended too that Puppet doesn't process the property any further?

This message was deleted.

This message was deleted.

This message was deleted.

Good day Puppet Community hattip ☕ This is just a reminder of the upcoming maintenance on the Forge this Wednesday 👇 https://puppetcommunity.slack.com/archives/C0W298S9G/p1689068073536019 Thanks!

Hello dear people I’m trying to setup a brand new Puppet infra based on Puppet 8 This is the very first node, that is supposed to be Complier, master and PuppetDB I have a problem that it can’t find the hieradata that are based on facts This is from the

--debug

run of the very first puppet apply for the node itself

Global Data Provider (hiera configuration version 5)
      Using configuration "/etc/puppetlabs/puppet/hiera.yaml"
      Hierarchy entry "Host data"
        Path "/etc/puppetlabs/code/hieradata/.yaml"
          Original path: "%{::facts.hostname}.yaml"
          Path not found

My

hiera.yaml

looks like this

defaults:
  datadir: /etc/puppetlabs/code/hieradata
  data_hash: yaml_data
hierarchy:
  - name: Host data
    path: "%{::facts.hostname}.yaml"
  - name: Host secure data
    lookup_key: eyaml_lookup_key
    path: "%{::facts.hostname}.eyaml"
    options:
      pkcs7_private_key: /etc/puppetlabs/puppet/eyaml/private_key.pkcs7.pem
      pkcs7_public_key: /etc/puppetlabs/puppet/eyaml/public_key.pkcs7.pem

This shows the facts are working

# puppet facts hostname
{
  "hostname": "us1svcs-uupuppetserver001"
}

However this doesn’t work

# puppet lookup --environment prod --explain --node us1svcs-uupuppetserver001 hostname
Error: Cached facts for us1svcs-uupuppetserver001 failed: Could not find terminus puppetdb for indirection facts
Error: Could not run: No facts available for target node: us1svcs-uupuppetserver001

Fixed thanks to @vchepkov Changed the hiera to look for

%{facts.networking.hostname}

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.