-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: renaming filteres #130
Comments
filtering like with other would work |
So If I understand correctly, you get a slug collision when naming two datacenters the same way (but different case): source:
- name: TestDC
type: ovirt
...
- name: TESTDC
type: vcenter
... |
Yes, it is correct. With some massive deployments resolving such problems in Hyperviaors might be 'complicated' and take time. A way to rename / remat ClusterGroups would ease onboarding |
Ok understandable, so I can add an option like this in config.yaml:
Or do you suggest different approach? |
I this this approach is good, thus I would call it consistently with other relation mappings, like: |
Yeah I agree. |
🎉 This issue has been resolved in version 0.6.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Support with search/replace for vc/ovirt Datacenter renames. The case if where in different systems admins used different names, aga:
ovirt: TestDC
vcenter: TESTDC
Currently it creates slug collision, would be good to being able to merge them by rewriting it for one of the sources.
The text was updated successfully, but these errors were encountered: