Contributions are welcome via GitHub Pull Requests. All PRs should be submitted against the unstable branch, where they will undergo review by a Broadcom APIM team member.
***Note: *** Raising PRs against one Chart at a time will speed up the release process.
- Fork this repository, develop, and test your changes.
- Submit a pull request against the unstable branch.
When submitting a PR make sure that it:
- Must pass internal application testing and GitHub CI jobs for linting and different k8s platforms (Managed by Broadcom and Github Actions).
- Implement changes in both files if the chart contains a values-production.yaml and a values.yaml.
- Any change to a chart requires a version bump following semver.
- A chart's
README.md
must include any additional configuration options. - The title of the PR starts with chart name (e.g.
[charts/gateway]
)
Note: Check/Raise a bug feature request first, this will save you time if there's something that's already known/in progress.
- Changes are automatically linted and tested using the
ct
tool as a GitHub action. Those tests are based onhelm lint
andkubeval
- Changes are manually reviewed by Broadcom APIM team members.
- Once the changes are accepted, the PR is tested (if needed) into the Broadcom CI pipeline, the chart is installed and tested (verification and functional tests).
- When the PR passes all tests, the PR is merged by the reviewer(s) in the GitHub
master
branch. - On merge, the Chart is pushed to the layer7 Chart Repository
Tips:
- A description. What did you expect to happen? What actually happened? Why do you think the behavior was incorrect?
- Provide any logs or relevant output.
- What version are you running when reproducing issue? What was the last version that the feature worked?
- Anything else that seems relevant.