ClubCedille / ClubCedille/k8s-shared
Ingénieuses: Investiguer pourquoi les mises-à-jour ne sont pas automatiques
Open
Nobody has claimed this yet.
- Dominant language
- YAML
- Stars
- 3
- Forks
- 1
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 101
Description
Les CMS des ingénieuse est sensé mettre à jour le site en publiant une nouvelle image docker, mais ce n'est plus le cas. Peut-être dû au changement des permissions des groupes utilisateurs dans l'organisation
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the repository's YAML and Argo CD configuration for the CMS deployment and its Docker image update mechanism. Check whether organization group permissions prevent the update, and consider the issue done when publishing a new image once again triggers the expected site update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github, kubernetes
- Domain
- authorization, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100