Need clarification on parameters in node object

Problem:
I just want to know what is parameters in node object yaml file when created with foreman ENC.
I am thinking that these are parameters for specific host provided by foreman not puppet. Am i correct?
I have sample yaml file-

classes:
api:
foreman_pass: puppet_provider
foreman_url: https://secpatchsrv.localdomain
foreman_user: puppet_provider
configmonitor:
elk::elkcert:
mcafeeens::windows::install_mcafee_win:
winr8:
as_atm_hgw_gateway: ‘’
as_atm_hgw_ip: ‘’
as_atm_hgw_mask: ‘’
as_hostname: ‘’
sma_tile_server: https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png
snd_appsrv_app_hgw_ip: 192.168.21.5
snd_appsrv_atm_hgw_ip: 192.168.66.5
snd_appsrv_hostname: secondappsrv
tc_app_hgw_gateway: 192.168.16.1
tc_app_hgw_ip: 192.168.21.110
tc_app_hgw_mask: 255.255.240.0
tc_printer01_ip: 192.168.100.120
tc_printer01_type: Epson AL-C300N Advanced
tc_screen_settings: 1x2_1920x1200
tc_swap_out: false
tc_tcts: false
termsrv_app_hgw_gateway: ‘’
termsrv_app_hgw_ip: ‘’
termsrv_app_hgw_mask: ‘’
termsrv_dmz_hgw_gateway: ‘’
termsrv_dmz_hgw_ip: ‘’
termsrv_dmz_hgw_mask: ‘’
termsrv_hostname: ‘’
termsrv_passwd: ‘’
termsrv_t3k_fw_ext_ip: ‘’
termsrv_t3k_nw_address: 192.168.16.0
vm_archsrv: 1stAppSrv
vm_r8_app_hgw_gateway: 192.168.16.1
vm_r8_app_hgw_ip: 192.168.21.212
vm_r8_app_hgw_mask: 255.255.240.0
vm_r8_hostname: vmr8
vm_ts_app_hgw_gateway: 192.168.16.1
vm_ts_app_hgw_ip: 192.168.21.211
vm_ts_app_hgw_mask: 255.255.240.0
vm_ts_atm_hgw_ip: 192.168.66.156
vm_ts_atm_hgw_mask: 255.255.248.0
vm_ts_ext_hgw: true
vm_ts_ext_hgw_ip: 192.168.123.101
vm_ts_ext_hgw_mask: 255.255.255.128
vm_ts_hostname: vmts
winr8::rsakeyexchange:
winr8::runstages:
winr8::t3kr8::tcnode:
parameters:
puppetmaster: secpatchsrv.localdomain
domainname: localdomain
hostgroup: ThinClient
puppet_ca: secpatchsrv.localdomain
foreman_env: production
owner_name: Admin User
owner_email: root@localdomain
ssh_authorized_keys:
foreman_users:
admin:
firstname: Admin
lastname: User
mail: root@localdomain
description:
fullname: Admin User
name: admin
ssh_authorized_keys:
foreman_subnets:

  • name: deployment
    network: 192.168.16.0
    mask: 255.255.240.0
    gateway: 192.168.16.1
    dns_primary: 192.168.21.17
    dns_secondary:
    from: 192.168.21.210
    to: 192.168.21.220
    boot_mode: DHCP
    ipam: DHCP
    vlanid:
    network_type: IPv4
    foreman_interfaces:
  • ip: 192.168.21.110
    ip6: ‘’
    mac: 68:05:ca:1c:4f:94
    name: tcz440.localdomain
    attrs: {}
    virtual: false
    link: true
    identifier: ‘’
    managed: true
    primary: true
    provision: true
    subnet:
    name: deployment
    network: 192.168.16.0
    mask: 255.255.240.0
    gateway: 192.168.16.1
    dns_primary: 192.168.21.17
    dns_secondary:
    from: 192.168.21.210
    to: 192.168.21.220
    boot_mode: DHCP
    ipam: DHCP
    vlanid:
    network_type: IPv4
    subnet6:
    tag:
    attached_to:
    type: Interface
  • ip:
    ip6:
    mac:
    name:
    attrs: {}
    virtual: false
    link: true
    identifier: ethernet 2
    managed: false
    primary: false
    provision: false
    subnet:
    subnet6:
    tag:
    attached_to:
    type: Interface
    foreman_config_groups:
    config_mode: DCS
    is_tomec: ‘false’
    linux_timezone: Asia/Calcutta
    ntp_server_1: 192.168.70.76
    ntp_server_2: 192.168.70.77
    version_delivery: 18.003.00
    win_timezone: India Standard Time
    environment: production

Hi,

you are basically correct.
The information under parameters are a collection of the following:

  • Host/Hostgroup parametes
  • Global Parameters
  • Automaticall generated information like the hashes with network information
  • (Maybe I forgot something)

Those are not directly related to you Puppet classes in any way, but they can be accessed from puppet code as topscope variables from ENC.

Regards