Meraki

mikefredrik · ‎Oct 14 2024

Yes that will be the workflow Little annoying that when you read the schema definition most of the parameters are defined/explained. I used the same in my code basically just like you, create the basic and then update with specifics

mikefredrik · ‎Oct 14 2024

Hi I've noticed that when I use the API to create VLANs on the MX there might be an error in the API. I use the createNetworkApplianceVlan with the following parameters: (some are comming from a few input statment and will later be part of a data flow between different systems) network_id, id_, name='test60', subnet='60.30.20.0/24', applianceIp='60.30.20.1', ipv6={'enabled': True,}, dhcpHandling='Run a DHCP server', dhcpLeaseTime ='1 hour', dnsNameservers='opendns' The two thing that is not reflected in the dashboard is Leasetime and DNS name server, the dashboard use the default upstream DNS and 1 day leasetime, not really what I want, event tried the swagewr on the meraki.io page to make sure I didn't have any type that will cause the API to use defaults. My current workaround is to then run the updateNetworkApplianceVlan with the following input: network_id, vlan_id, name=vlan_name, <This is from an input string dhcpLeaseTime='1 hour', dnsNameservers='opendns' Now the DHCP settings reflect what I want As always it could be error code 40 (problem 40 cm from the keyboard) but also something else. Ideas / Input appriciated //Mikael

mikefredrik · ‎Aug 28 2024

Aware of the possibilities to use the vault to encrypt the file, the thing is I have not found out how to use this in the playbook. The content of the encrypted credentials file is something like this (omitted) ansible@ubuntu-c:~$ cat credentials.yml $ANSIBLE_VAULT;1.1;AES256 30373530356435393538623861663236306130343136376434326166656638313763356537356239 623436 So how to referense to this in the playbook

mikefredrik · ‎Aug 28 2024

Found one working solution after some testing. Provide the credential file in the execution of the playbook. ansible-playbook -e @Api_key.yml webhook.yaml api_key.yml contain the following: --- meraki_api_key: 'my secret key' eof in the playbook I added meraki_api_key: "{{ meraki_api_key }}" in the task part of the book

mikefredrik · ‎Aug 28 2024

New to Ansible with a better understanding of RestAPI I'm in the beginning of my learning to write Ansible playbooks. Currently I like to avoid using the export command or hard-code the API-Key in to the playbook. The solution seams to be to create a credentials.yml file with the API-key. I follow the guide on this link https://github.com/meraki/dashboard-api-ansible/blob/main/playbooks/credentials.yml So the file looks like this: --- meraki_api_key: "my key" end-of-file My playbook yml file I try to use looks like the following: --- - hosts: meraki_servers gather_facts: false tasks: - name: Get all webhooks httpservers cisco.meraki.networks_webhooks_http_servers_info: meraki_suppress_logging: true networkId: 'My network-ID' register: result - name: Show current WebHook Servers ansible.builtin.debug: msg: "{{ result }}" end-of-file If I add meraki_api_key: "My key " befire the networkId line it works if not I receive an error saying meraki_api_key is missing Ideas?

Meraki

Community

About mikefredrik

mikefredrik

API Early Access Group

Community Record

Badges

Re: Create VLAN using API on MX

Create VLAN using API on MX

Re: Adding API-Key to the credentials.yml

Re: Adding API-Key to the credentials.yml

Adding API-Key to the credentials.yml