Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for on-prem JAMF instances #2

Open
innowintay opened this issue Apr 10, 2021 · 0 comments · May be fixed by #3
Open

Allow for on-prem JAMF instances #2

innowintay opened this issue Apr 10, 2021 · 0 comments · May be fixed by #3

Comments

@innowintay
Copy link

Thanks for this most recent update! I'm actually in the process of rolling out Backblaze using JAMF to my company and had just perfected my adaptations of the older script when I noticed this one had been updated to fix the error reporting.

I saw where you requested that we enter an issue before PRing any major changes. The way you had the JAMF URL scripted prevents anyone using JAMF on-prem from using this script without adaptation. I'm going to PR a change that not only allows users to enter the full FQDN but also ensures it strips the HTTP/HTTPS protocol if they should happen to include it.

@innowintay innowintay linked a pull request Apr 10, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant