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

Use headers only #446

Merged
merged 11 commits into from
Oct 4, 2019
Merged

Use headers only #446

merged 11 commits into from
Oct 4, 2019

Conversation

ssc3
Copy link
Contributor

@ssc3 ssc3 commented Sep 25, 2019

Datadog now accepts api and app keys in headers. This PR modified datadogpy to pass api and app keys in headers only.

@ssc3 ssc3 requested a review from a team as a code owner September 25, 2019 17:18
Copy link
Contributor

@zippolyte zippolyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !

@bkabrda
Copy link
Contributor

bkabrda commented Sep 26, 2019

/azp run DataDog.datadogpy.integration

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@bkabrda bkabrda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm seeing a lot of integration test failures that I haven't seen without this PR. Specifically:

  • Any integration tests that try to send metrics fail with 403.
  • Any integration tests that try to create events fail with 403.
  • Any integration tests that try to post service check statuses fail with 403.

Have these API endpoints been adapted to respect the headers? If not, they'll need to be before we can accept this PR (alternatively we would need to differentiate which endpoint the HTTP request is being sent to and based on that we'd need to add headers or query params)

@bkabrda
Copy link
Contributor

bkabrda commented Oct 2, 2019

/azp run

@bkabrda
Copy link
Contributor

bkabrda commented Oct 2, 2019

/azp run DataDog.datadogpy.integration

@ssc3
Copy link
Contributor Author

ssc3 commented Oct 2, 2019

/azp run

@azure-pipelines
Copy link

Comment was made before the most recent commit for PR 446 in repo DataDog/datadogpy

1 similar comment
@azure-pipelines
Copy link

Comment was made before the most recent commit for PR 446 in repo DataDog/datadogpy

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@ssc3
Copy link
Contributor Author

ssc3 commented Oct 2, 2019

/azp run DataDog.datadogpy.integration

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ssc3
Copy link
Contributor Author

ssc3 commented Oct 4, 2019

/azp run DataDog.datadogpy.integration

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@zippolyte zippolyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ssc3 ssc3 merged commit b4cb2df into master Oct 4, 2019
@ssc3 ssc3 deleted the shubho/headers-only branch October 4, 2019 16:54
dabcoder pushed a commit to dabcoder/datadogpy that referenced this pull request Oct 25, 2019
* Use headers only

* Check if api_key is required in params for some endpoints

* Add unit test for api_keys in params

* Fix blank lines

* Remove more spaces

* Add a set of excluded paths

* flake

* flake8

* Flake8 on another file
dabcoder pushed a commit to dabcoder/datadogpy that referenced this pull request Nov 28, 2019
* Use headers only

* Check if api_key is required in params for some endpoints

* Add unit test for api_keys in params

* Fix blank lines

* Remove more spaces

* Add a set of excluded paths

* flake

* flake8

* Flake8 on another file
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 this pull request may close these issues.

None yet

3 participants