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

feat: add noProxy field to repository & repository templates #18526

Merged
merged 1 commit into from
Aug 20, 2024

Conversation

the-technat
Copy link
Contributor

@the-technat the-technat commented Jun 6, 2024

Adds support for noProxy on repository & repository templates

Closes #18323

Thanks to @chetan-rns for adding the initial first-class proxy support! Adding noProxy to this existing feature was thus made rather easy.

I can confirm that the feature works as intended. It was tested locally and inside Swiss Post's EKS environment (dev stage). If someone wants to test as well, I built the image with the PR-commit state.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 3 times, most recently from 7c5c4b1 to e7a3a5f Compare June 6, 2024 15:03
Copy link

codecov bot commented Jun 6, 2024

Codecov Report

Attention: Patch coverage is 96.47059% with 3 lines in your changes missing coverage. Please review.

Project coverage is 55.87%. Comparing base (74af92f) to head (68c1a79).
Report is 1 commits behind head on master.

Files Patch % Lines
cmd/argocd/commands/repo.go 0.00% 1 Missing ⚠️
cmd/util/repo.go 0.00% 1 Missing ⚠️
reposerver/repository/repository.go 92.85% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master   #18526      +/-   ##
==========================================
+ Coverage   55.86%   55.87%   +0.01%     
==========================================
  Files         316      316              
  Lines       43741    43763      +22     
==========================================
+ Hits        24434    24452      +18     
- Misses      16745    16754       +9     
+ Partials     2562     2557       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 2 times, most recently from 8b84fa7 to a8875fd Compare June 7, 2024 08:03
@the-technat the-technat marked this pull request as ready for review June 7, 2024 08:35
@the-technat the-technat requested review from a team as code owners June 7, 2024 08:35
@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 4 times, most recently from 0c4bf79 to 7bb889b Compare June 14, 2024 10:00
Copy link
Member

@mkilchhofer mkilchhofer left a comment

Choose a reason for hiding this comment

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

@the-technat gave me a demo in Swiss Posts environment. Worked like a charm 😎

@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 8 times, most recently from 2de3343 to 1663ff8 Compare June 20, 2024 12:53
@agaudreault agaudreault self-requested a review June 21, 2024 19:22
docs/operator-manual/declarative-setup.md Outdated Show resolved Hide resolved
@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 4 times, most recently from 7da6d74 to ea0eee6 Compare June 24, 2024 09:29
Copy link
Contributor

@todaywasawesome todaywasawesome left a comment

Choose a reason for hiding this comment

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

Looks good!

@the-technat the-technat force-pushed the feat/repo-creds-no_proxy branch 2 times, most recently from 572383f to f0b899e Compare August 20, 2024 11:06
@crenshaw-dev crenshaw-dev enabled auto-merge (squash) August 20, 2024 13:41
@blakepettersson
Copy link
Member

@the-technat there are some conflicts which needs to be resolved.

auto-merge was automatically disabled August 20, 2024 15:08

Head branch was pushed to by a user without write access

Signed-off-by: Nathanael Liechti <technat@technat.ch>
@crenshaw-dev crenshaw-dev merged commit bacdced into argoproj:master Aug 20, 2024
27 of 28 checks passed
@mkilchhofer
Copy link
Member

❤️ 🙏

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.

Add no_proxy field to repo-creds
7 participants