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

docs(proposal): support for post renderers #16749

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

surajnarwade
Copy link

@surajnarwade surajnarwade commented Jan 4, 2024

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).

@surajnarwade surajnarwade requested review from a team as code owners January 4, 2024 13:09
@surajnarwade surajnarwade force-pushed the post-render-support branch 3 times, most recently from 1f34c40 to 0c697e9 Compare January 4, 2024 13:24
@surajnarwade
Copy link
Author

surajnarwade commented Jan 4, 2024

Copy link

codecov bot commented Jan 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 49.48%. Comparing base (f87897c) to head (e8d3bbc).
Report is 416 commits behind head on master.

Current head e8d3bbc differs from pull request most recent head d532fd7

Please upload reports for the commit d532fd7 to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #16749      +/-   ##
==========================================
- Coverage   49.73%   49.48%   -0.25%     
==========================================
  Files         274      271       -3     
  Lines       48948    47728    -1220     
==========================================
- Hits        24343    23620     -723     
+ Misses      22230    21773     -457     
+ Partials     2375     2335      -40     

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

Signed-off-by: surajnarwade <[email protected]>
...
helm:
...
postRenderers:
Copy link
Contributor

Choose a reason for hiding this comment

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

While the proposal naming comes from Helm's post-renderer feature, this proposal isn't expecting to use it directly, and indeed has a custom implementation for kustomize.

To be more broadly useful could this be under source.postRenderers instead, applying to any sort of application source? (e.g. you might want to post-render some external repo container kustomize, or some custom plugin)

Copy link
Member

Choose a reason for hiding this comment

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

Agreed. I think source.kustomizePatches makes sense.

Whether or not we nest it in a postRenderers list is another question.

Copy link
Author

Choose a reason for hiding this comment

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

make sense, I have moved the postRenderers under the source field now

Copy link
Author

Choose a reason for hiding this comment

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

thanks @mikebryant :) @crenshaw-dev I've moved the struct and also linked the POC.

@surajnarwade
Copy link
Author

surajnarwade commented Jan 9, 2024

I have the POC on my fork: surajnarwade/argo-cd@5bb7cd9...a399863 for the same.

@aguckenber-chwy
Copy link

aguckenber-chwy commented Feb 15, 2024

Heyo, any ETA on when you may get the feature in? I need to use a private helm chart and customize it which is s a LOT more painful than I expected and my options are either to hack it with Kustomize (i.e. this issue) and a Plugin, else if this feature is very soon going to be released I would just use this :)

@mikebryant
Copy link
Contributor

@crenshaw-dev Is there anything more we need to do here, or can this proposal be accepted?

@surajnarwade
Copy link
Author

surajnarwade commented Mar 28, 2024

@crenshaw-dev Is there anything more we need in this proposal, can you review again please, TIA 🙏

@zachaller
Copy link
Contributor

I feel like this could be done via a CMP not?

@todaywasawesome
Copy link
Contributor

I agree, this is what CMPs are for.

@afarbos
Copy link
Contributor

afarbos commented Jan 3, 2025

I feel like this could be done via a CMP not?

Can you send what argocd generate into a CMP?

If it's straightforward maybe this should be an option in the argocd helm chart seeing with the demand for it. It does not seems has straightforward to me between file management, patches to generate and more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for final review
Development

Successfully merging this pull request may close these issues.

10 participants