openwisp / openwisp/openwisp-controller
[feature] Allow specifying one or multiple tags in geographic locations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
This is up for discussion and it could be an alternative to #712, or both features could be implemented if there's not too much complexity.
We could allow to specify one or multiple tags in a geographic location, so that if a device is tagged with the tag used by the location, the device gets the location assigned to it and the template tagged with that tag as per #711.
This could be useful if groups are bein used to group devices based on traits that have nothing to do with the location, but could be grouped by type (eg: Routers, WiFI Access Points, 4G Routers, etc), in this case, assigning a location to a group will not work, so if the user still needs to assign specific config logic depending on the location, they could do so with tags.
Contributor guide
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, tests, or entry points are named. Start by reading issues #711 and #712, then identify the existing location, device-tag, group, and template-assignment paths; done requires an agreed scope for single and multiple tags plus tests covering the intended assignment behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100