opendevstack / opendevstack/ods-core
Make Nexus config script idempotent
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 53
- Forks
- 34
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 1
Description
nexus/configure.sh can only be used for the initial setup, as it does not check what resources already exist in Nexus. Given that it uses Groovy, it should be possible to check for existence for each resource before creating it, making the script idempotent. Of course, changing config of a resource wouldn't work well still, but that is complicated anyway. I guess the best approach is to always create new resource when config should be changed.
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 with nexus/configure.sh and read how its Groovy-based setup creates each Nexus resource. Determine how existing resources should be detected before creation, then verify that rerunning the script does not create duplicates; configuration changes remain outside the stated scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100