ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Rename a context value fails to update existing configurations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
We have a context (Environment, Service, Instance)
If i were to rename one of the already created Instances say (testing2->testing3), the corresponding configurations that were originally tied to testing2 are not updated. So if we have a bunch of configurations tied to one of these names and want to change them, it becomes tedious through the UI. One thing to note that if you do look at properties associated to testing3 it still shows testing2 properties on the rename page. And if you query for those something with testing3 context it will not return back those configurations.
Version 1.8.2
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
Start by tracing the UI rename flow for an Instance and the configuration lookup by context. Verify how properties and configurations are associated before and after renaming testing2 to testing3; done means existing configurations and their properties are available through the new context, and queries using testing3 return them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100