-
Notifications
You must be signed in to change notification settings - Fork 43
✨ Adding the c-sharp provider extension to be used in the hub. #503
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
base: main
Are you sure you want to change the base?
✨ Adding the c-sharp provider extension to be used in the hub. #503
Conversation
WalkthroughAdds a Tech Preview C# provider across CI, bundle/release, Helm chart, CSV, install scripts, Ansible defaults, and extension templates by wiring a new provider image/value and adding a C# Extension resource; all changes are additive configuration and manifest updates. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (5 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
* This is the updated tech preview c-sharp extension based from github.com/konveyor/c-sharp-analyzer-provider Signed-off-by: Shawn Hurley <[email protected]>
3aa9132 to
1a841a8
Compare
|
We should hold until this is tested in konveyor/analyzer-lsp#965 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
.github/actions/make-bundle/action.yml(2 hunks).github/workflows/create-release.yml(1 hunks)bundle.Dockerfile(1 hunks)bundle/manifests/konveyor-operator.clusterserviceversion.yaml(3 hunks)hack/install-tackle.sh(2 hunks)helm/templates/deployment.yaml(1 hunks)helm/values.yaml(1 hunks)roles/tackle/defaults/main.yml(1 hunks)roles/tackle/templates/customresource-extension.yml.j2(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: run-ci / e2e-api-integration-tests
🔇 Additional comments (11)
helm/values.yaml (1)
26-26: LGTM!The new C# provider image entry follows the established pattern for other provider images.
helm/templates/deployment.yaml (1)
60-61: LGTM!The environment variable follows the established pattern for related images and correctly references the Helm value.
bundle/manifests/konveyor-operator.clusterserviceversion.yaml (2)
356-357: LGTM!The environment variable addition follows the established pattern for provider images.
559-560: LGTM!The relatedImages entry correctly follows the naming convention used by other providers.
.github/actions/make-bundle/action.yml (2)
56-59: LGTM!The new input definition follows the established pattern for provider image inputs.
101-101: LGTM!The conditional OPTS handling is consistent with other provider inputs.
hack/install-tackle.sh (2)
28-28: LGTM!The environment variable follows the established pattern for provider images.
131-131: LGTM!The Tackle CR spec field is consistent with the existing Java provider configuration.
.github/workflows/create-release.yml (1)
224-224: Consider adding a wait step for the C# provider image.Other provider images like
java-analyzer-bundlehave explicit wait steps to ensure the image is available before proceeding with the bundle build. Consider adding a similar wait step for thec-sharp-providerimage to prevent build failures if the image isn't published yet during a release.roles/tackle/templates/customresource-extension.yml.j2 (1)
186-189: Likely copy-paste error inpaket_cmdpath.The
paket_cmdvalue points to the same path asilspy_cmd(/root/.dotnet/tools/ilspy_cmd). This appears incorrect — it should reference a distinct paket binary, likely/root/.dotnet/tools/paketor similar.- providerSpecificConfig: ilspy_cmd: "/root/.dotnet/tools/ilspy_cmd" - paket_cmd: "/root/.dotnet/tools/ilspy_cmd" + paket_cmd: "/root/.dotnet/tools/paket"Verify the correct path for the paket command in the C# provider image.
roles/tackle/defaults/main.yml (1)
183-192: Verify environment variable propagation across deployment infrastructure.The C# provider configuration correctly follows the established pattern used by Python, Node.js, and Java providers: consistent naming conventions, appropriate resource allocations (1 CPU, 1Gi memory), and proper environment variable lookup syntax.
However, verify that
RELATED_IMAGE_PROVIDER_C_SHARPis properly defined and propagated through the deployment infrastructure (Helm templates, operator manifests, GitHub Actions, bundle configuration). Without confirmation that this environment variable is wired across all deployment paths, the configuration alone may be incomplete.
dymurray
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This currently doesn't work because of the hub's selector regex failing to match but I want this in to help test and fix that bug
dymurray
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind this actually breaks all tech discovery
Signed-off-by: Dylan <[email protected]>
28e9abd to
f72ec5f
Compare
Co-authored-by: Maayan Hadasi <[email protected]> Signed-off-by: Shawn Hurley <[email protected]>
mguetta1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #504
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.