Enable the Puppet Core repositories on Apt

Download the package and run the dpkg tool in install mode:
Copy
```
wget --content-disposition <PACKAGE_URL>
sudo dpkg -i <FILE_NAME>.deb
```

For example, to enable the Ubuntu focal repository:

Copy

wget --content-disposition https://apt-puppetcore.puppet.com/public/puppet8-release-focal.deb
sudo dpkg -i puppet8-release-focal.deb

Edit the /etc/apt/auth.conf.d/<FILE_NAME>.conf file to add the credentials:
Copy
```
#login forge-key
#password <API_KEY>
```
forge-key is a string literal. API_KEY is the Forge API key associated with your free or paid Puppet Core user. See Purchasing Puppet Core and Accessing Puppet Core for limited use for testing or development.

You must use forge-key to download Puppet Core packages from yum-puppetcore.puppet.com or apt-puppetcore.puppet.com. However, either forge-key or license-id (associated with Puppet Enterprise) can be used to download artifacts from artifacts-puppetcore.puppet.com and Ruby gems from rubygems-puppetcore.puppet.com.

See the following example:
Copy
```
$ sudo vi /etc/apt/auth.conf.d/apt-puppetcore-puppet.conf
machine apt-puppetcore.puppet.com
login forge-key
password <API_KEY>
```
Update the apt package lists:
Copy
```
sudo apt-get update
```

Results: Certain operating systems and installation methods automatically verify package signatures. In these cases, you don’t need to do anything to verify the package signature. These methods include:

If you install from the Puppet Yum and Apt repositories, the release package that enables the repository also installs our release signing key. The Yum and Apt tools automatically verify the integrity of packages as you install them.
If you install a Windows agent using an .msi package, the Windows installer automatically verifies the signature before installing the package.
If you need to manually verify packages, see Verify packages.
If you install a .dmg package on macOS, the installer automatically verifies the signature before installing the package.