Puppet facts not populating after 61b10ea7fc1861bd334f14aad456d3027592e68f about puppet-network HOT 6 CLOSED

We use this fact internally as hiera like so:

nat_gateway::public_interface: "%{::network_primary_interface}"

I confirmed by viewing puppet logs that this fact stopped working exactly when this commit happened, and I also verified the hashes of the file before and after based on the puppet logs:
content changed '{md5}9164ece59c43998af1efb392c0023ff6' to '{md5}6d9bca1d4813ea164f4a46b654fa0f66'

Curiously, I patched our hiera to use the networking.primary fact, and now the module fact shows up, albeit under a different name:

root@box:~$ facter -j -p ':network_primary_interface'
{
  ":network_primary_interface": "eth0"
}

root@box:~$ facter -j -p 'network_primary_interface'
{
  "network_primary_interface": ""
}

I do not know what the root cause issue is.

from puppet-network.

Ahh, I didn't notice at first, but that commit added colons to the beginnings of all the facts that used to exist...

Why? Why break things?

EDIT: Were you trying to use ruby symbols instead of strings?

from puppet-network.

61b10ea was in #268.

from puppet-network.

Right, facts are being generated with names with leading colons:

from puppet-network.

EDIT: Were you trying to use ruby symbols instead of strings?

This seems very likely.

from puppet-network.

Fixed in #278

from puppet-network.