Use https:// in datadog-reports.yaml#503
Merged
truthbk merged 1 commit intoDataDog:masterfrom Mar 15, 2019
cabrinha:reports
Merged
Use https:// in datadog-reports.yaml#503truthbk merged 1 commit intoDataDog:masterfrom cabrinha:reports
truthbk merged 1 commit intoDataDog:masterfrom
cabrinha:reports
Conversation
truthbk
approved these changes
Mar 15, 2019
Member
truthbk
left a comment
There was a problem hiding this comment.
This is a regression and is consistent with the client docs here: https://github.com/DataDog/dogapi-rb
Thank you so much! 🙇
cegeka-jenkins
pushed a commit
to cegeka/puppet-datadog_agent
that referenced
this pull request
Apr 6, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Without specifying https://, I get this error:
In #488 one user claimed to have success by changing this URL to use HTTPS: krux#1
I've also tested this myself and found it resolves the error shown above.
The puppet versions I'm running are:
@truthbk please have a look!