fix: update ARGOCD_REPO_SERVER_PLUGIN_USE_MANIFEST_GENERATE_PATHS env…

[kpanter]

… for argocd-repo-server deployment

our validation workflow detected below error
❌ FAIL: stdin - Deployment argocd-repo-server is invalid: problem validating schema. Check JSON formatting: jsonschema: '/spec/template/spec/containers/0/env/21' does not validate with https://github.com/yannh/kubernetes-json-schema/master/master-standalone-strict/deployment-apps-v1.json#/properties/spec/properties/template/properties/spec/properties/containers/items/properties/env/items/additionalProperties: additionalProperties 'configMapKeyRef' not allowed

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

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.87%. Comparing base (ca91dd9) to head (8b5f373).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #20131      +/-   ##
==========================================
+ Coverage   55.86%   55.87%   +0.01%     
==========================================
  Files         321      321              
  Lines       44492    44492              
==========================================
+ Hits        24854    24860       +6     
+ Misses      17072    17068       -4     
+ Partials     2566     2564       -2     

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

[crenshaw-dev]

@kpanter good catch. The install.yaml is rendered based on Kustomize manifests, so the primary problem is in a different file. Once you find that file, you can run make manifests-local to regenerate install.yaml.

[blakepettersson]

This is a duplicate of #20139 right?

[kpanter]

@kpanter good catch. The install.yaml is rendered based on Kustomize manifests, so the primary problem is in a different file. Once you find that file, you can run make manifests-local to regenerate install.yaml.

Updated argocd-repo-server-deployment.yaml under manifests/base/repo-server and executed make manifests-local

[kpanter]

This is a duplicate of #20139 right?

yes, right

[kpanter]

duplicate of #20139