Skip to content

Refactor developer experience for this repo #1168

@etsauer

Description

@etsauer

Feature description

  • Remove the duplicate helm charts (currently one in /charts and one in /pelorus-operator/helm-charts). moving forward there will only be one chart
  • Make the pelorus-operator/ directory the new project root. There will be some merging of ideas on concepts here, but I think treating that directory as "the project" instead of a set of resources that get generated will allow us to reduce some other complexities. At this point the chart in pelorus-operator/helm-charts will be what we make direct changes to. this will allow us to...
  • Eliminate the patch files we were using to modify the operator config. Since we won't be re-generating the operator on each change, we don't need to keep them separate anymore.
  • Reduce the number of places where we have release versions hard coded in files. This will allow us to simplify a bunch of the scripts we rely on to do version updates and other repo maintenance.
  • start a new dev guide, since a lot of our processes documented will change
  • Refactor the python dependency management in a way that dependabot changes are mergeable
  • (stretch goal) Move the chart-lint and version updates to a post-commit activity... meaning CI does it for us instead of it being a blocker to make a commit. Not sure exactly how i'll accomplish that yet but I want to try.

How this will help you

This will reduce the complexity of getting PRs opened, reviewed and merged

Feature priority

⌛ It will greatly improve my experience using Pelorus

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions