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

meraki_alert module issue - "ERROR! 'meraki_alert' is not a valid attribute for a Play #301

Open
aaljawahiri opened this issue Apr 7, 2022 · 4 comments
Labels
waiting_for_response Waiting for response from someone

Comments

@aaljawahiri
Copy link

aaljawahiri commented Apr 7, 2022

I'm just doing some testing with the Ansible Meraki module using meraki_alert. Am I doing something wrong? I keep getting the below error:

image

"ERROR! couldn't resolve module/action 'meraki_alert'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/beardwin/meraki-ansible/playbooks/alerts.yml': line 4, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

    tasks:
    - name: Query all settings
      ^ here"

Is there also a way to find out all the possible values the "type" parameter can take? For example, one of the values would be "gatewayDown" Is there a way to find all the possible values?

image

Using the below documentation.

https://docs.ansible.com/ansible/latest/collections/cisco/meraki/meraki_alert_module.html#parameters

By the way, Indentation seems to be fine, I can run the other Meraki Playbooks just fine with the same indentation, unless I'm being blind!

Thanks in advance for your help!

@aaljawahiri aaljawahiri changed the title Meraki Alert issue meraki_alert module issue - "ERROR! 'meraki_alert' is not a valid attribute for a Play Apr 7, 2022
@kbreit
Copy link
Collaborator

kbreit commented Apr 8, 2022

To my mind this looks fine but obviously there's something off. It seems like a syntax error to me. I'd recommend putting your playbook into a YAML validated and seeing what it says. Online ones may have access to the content so don't put sensitive content in it.

Regarding your question about possible values, in this case I don't think so. I looked at the API documentation and they don't list all the options. I'll ask if that's something that can be linked.

@aaljawahiri
Copy link
Author

To my mind this looks fine but obviously there's something off. It seems like a syntax error to me. I'd recommend putting your playbook into a YAML validated and seeing what it says. Online ones may have access to the content so don't put sensitive content in it.

Regarding your question about possible values, in this case I don't think so. I looked at the API documentation and they don't list all the options. I'll ask if that's something that can be linked.

Thanks, do let me know if you find anything. Does the module look fine to you?

@kbreit
Copy link
Collaborator

kbreit commented Apr 11, 2022

My module tests execute just fine. Not to say they're perfect. Far from it. Did you try putting your playbook through a YAML validation

@kbreit
Copy link
Collaborator

kbreit commented May 11, 2022

@Beardwin1 Following up. Were you able to validate the YAML? I could continue looking into it if it's still a problem

@kbreit kbreit added the waiting_for_response Waiting for response from someone label Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting_for_response Waiting for response from someone
Projects
None yet
Development

No branches or pull requests

2 participants