Skip to content

[buddy] fix: use proxy from env for compatible integrations#47663

Merged
tigrato merged 2 commits intomasterfrom
tigrato/pr-buddy-47611
Oct 18, 2024
Merged

[buddy] fix: use proxy from env for compatible integrations#47663
tigrato merged 2 commits intomasterfrom
tigrato/pr-buddy-47611

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Oct 17, 2024

  • fix: use proxy from env for pagerduty integration
  • feat: add proxy conf for integrations that support it

Closes #47604

Changelog: Respect HTTP_PROXY environment variables for Access Request integrations.

@tigrato tigrato self-assigned this Oct 17, 2024
@tigrato tigrato changed the title tigrato/pr buddy 47611 [buddy] fix: use proxy from env for compatible integrations Oct 17, 2024
@tigrato tigrato marked this pull request as ready for review October 17, 2024 13:42
Copy link
Copy Markdown
Contributor

@hugoShaka hugoShaka left a comment

Choose a reason for hiding this comment

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

I think we should be careful with backporting as this is potentially disruptive. We were happily ignoring HTTP_PROXY until now, but we'll start to honour them.

@tigrato tigrato enabled auto-merge October 18, 2024 18:23
@tigrato tigrato added this pull request to the merge queue Oct 18, 2024
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 18, 2024
@tigrato tigrato added this pull request to the merge queue Oct 18, 2024
Merged via the queue into master with commit 6ff4c25 Oct 18, 2024
@tigrato tigrato deleted the tigrato/pr-buddy-47611 branch October 18, 2024 19:40
@public-teleport-github-review-bot
Copy link
Copy Markdown

@tigrato See the table below for backport results.

Branch Result
branch/v14 Failed
branch/v15 Failed
branch/v16 Create PR

@tigrato
Copy link
Copy Markdown
Contributor Author

tigrato commented Oct 21, 2024

I think we should be careful with backporting as this is potentially disruptive. We were happily ignoring HTTP_PROXY until now, but we'll start to honour them.

I don't think this will be a major issue because most of the cases, proxies are used to bypass external connectivity limitations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PagerDuty Integration Does Not Respect HTTP_PROXY Environment Variables

4 participants