Skip to content
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

Different site_id for different clusters possible? #145

Open
a118n opened this issue Sep 4, 2023 · 0 comments
Open

Different site_id for different clusters possible? #145

a118n opened this issue Sep 4, 2023 · 0 comments
Assignees
Labels
accepted This issue has been accepted for implementation feature Introduction of new functionality to the application
Milestone

Comments

@a118n
Copy link

a118n commented Sep 4, 2023

Hello,
I can see that multi-cluster support was added to the plugin, but I can't seem to figure out how to define different site_id for each of the cluster.
For example I have the following clusters in the config:

PLUGINS_CONFIG = {
    'netbox_proxbox': {
        'proxmox': [
            {
                'domain': 'dc01-pve01.example.org',
                'http_port': 8006,
                'user': 'root@pam',
                'password': '123456',
                'ssl': False
            },
            {
                'domain': 'dc02-pve01.example.org',
                'http_port': 8006,
                'user': 'root@pam',
                'password': '123456',
                'ssl': False
            }
        ],
        'netbox': {
            'domain': 'localhost',
            'http_port': 8001,
            'token': 'abcgsuydsfkjdsklf12312',
            'ssl': False,
            'settings': {
                'virtualmachine_role_id' : 47,
                'node_role_id' : 29,
                'site_id': ???
            }
        }
    }
}

site_id is defined outside of clusters scope and is global for all of them?

@emersonfelipesp emersonfelipesp self-assigned this Oct 9, 2023
@emersonfelipesp emersonfelipesp added feature Introduction of new functionality to the application accepted This issue has been accepted for implementation labels Oct 9, 2023
@emersonfelipesp emersonfelipesp added this to the v0.0.8 milestone Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted This issue has been accepted for implementation feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants