You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to install from download_file location rather than contacting master? Would be beneficial when offline or off VPN with no connectivity to master and don't want to have to spin up a master in vagrant... makes pe_build useful for installing latest PE version on agent to do local applies with. (beats having to deal with latest boxes on atlas with 4.3.2 on them)
The text was updated successfully, but these errors were encountered:
This currently isn't supported by the pe_agent provisioner as it just calls through to the pe_repo module on the master. Looking at the top-level class in pe_repo, the staging directory where tarballs are stored is hard-coded to /opt/puppetlabs/server/data/staging and isn't exposed as a parameter. So it's not possible to configure pe_repo for a shared tarball cache.
The other option would be to add some logic to the provisioner to download and copy repo files outside of the provisioner --- but the code paths that handle that for pe_bootstrap aren't set up to handle agent version numbers. So, this is probably blocked on getting #97 done first so that pe_build is aware of PE version/agent version combinations instead of delegating that entirely to the pe_repo module.
Is there a way to install from download_file location rather than contacting master? Would be beneficial when offline or off VPN with no connectivity to master and don't want to have to spin up a master in vagrant... makes pe_build useful for installing latest PE version on agent to do local applies with. (beats having to deal with latest boxes on atlas with 4.3.2 on them)
The text was updated successfully, but these errors were encountered: