NSLS2 / NSLS2/nsls2.ioc_deploy
When deploying an IOC, write out all module configs used
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1
- Forks
- 26
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 13
Description
We should create files representing each module that was deployed. In the case of latest from #31 , we should get the commit hash of the HEAD and use that for the version.
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
No files or tests are named in the issue. Start by tracing the deployment entry point for module handling, then verify that each deployed module produces a config file and that deployments using latest record the HEAD commit hash as the version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100