-
AC:
- [ ] Using a baseline repositories yml file (`CURRENT_VER`), you can use a second repositories yml file (`NEW_VER`) to determine what versions should be included in the release and changelog. The…
sgnn7 updated
4 years ago
-
In the first release, we will tell users how to use docker-compose (quick start), the helm chart, and cloudformation templates with the suite release versions (eg share examples of how to configure wi…
-
We need to add automated end-to-end tests for Conjur OSS, but our e2e automation system is bloated and likely running many redundant tests.
Draft requirements (may be revised):
- Tests run in a reali…
-
An end-to-end test case exists using the pinned component versions for:
- Conjur OSS
- Conjur Helm Chart
- Kubernetes authenticator
- Secretless
-
Hi there,
There is no default behavior if the CONJUR_VERSION is not set, or not 4 or 5.
Code reference:
https://github.com/cyberark/conjur-authn-k8s-client/blob/master/pkg/authenticator/authentica…
-
All releases should publicly available so a developer only needs to use Maven/Gradle to pull this library into their project.
-
All public repos have bug and feature request issue templates.
Suggested templates:
- [Bug template](https://github.com/conjurinc/docs/blob/master/templates/issues/bug.md)
- [Feature request template…
-
AC:
- [ ] Every repo in the list below has a basic CONTRIBUTING.md file (template [here](https://github.com/conjurinc/docs/blob/master/reference/open_source/templates/CONTRIBUTING.md)) - add a file if…
-
- [x] Review all components in the suite release to determine whether they meet the standards for gh tags / releases defined in #42, and fix them if not.
- [x] Ensure each repo has documented guidelin…
-
Review this repo:
- [x] Determine whether improvements can be made to update/modernize the release process
- [x] Review README and CONTRIBUTING to determine if either documentation set is missing impo…