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
Not sure if this is a feature request or me unable to spot the correct approach, but it seems like the option to use a custom url for the installer assumes that the webserver does not require authentication. For my environments, the webserver will be a Nexus and each repository will require authentication.
So my question is - is there support for either providing basic authentication or alternatively downloading the installer before and somehow instructing chef_client_updater to not download the installer, but instead use a local path to my already downloaded installer?
The text was updated successfully, but these errors were encountered:
Not sure if this is a feature request or me unable to spot the correct approach, but it seems like the option to use a custom url for the installer assumes that the webserver does not require authentication. For my environments, the webserver will be a Nexus and each repository will require authentication.
So my question is - is there support for either providing basic authentication or alternatively downloading the installer before and somehow instructing chef_client_updater to not download the installer, but instead use a local path to my already downloaded installer?
The text was updated successfully, but these errors were encountered: