bonsai_asset plugin - GET request failed: timed out about sensu-go-ansible

[tadeboro]

Hi @michaeldeaton.

The bonsai_asset is an action plugin executed on the control node. What that plugin does is:

1. Download a list of all available asset versions from the bonsai (GET https://bonsai.sensu.io/api/v1/assets/sensu-plugins/sensu-plugins-memory-checks is the URL we hit for memory checks). We do this to make sure we have a valid version.
2. Get the asset definition for the selected version (GET https://bonsai.sensu.io/api/v1/assets/sensu-plugins/sensu-plugins-memory-checks/4.1.1/release_asset_builds). This is the actual data we need to create a new asset.

The data we retrieved with the second GET request is then used to construct the asset definition that is then fed to the asset module that does the actual creation.

I forgot what exactly was the reason for placing the download onto the control node, but I have a feeling that we did that because the control node usually has better internet access compared to target nodes. But I guess I was wrong about that ;)

Maybe adding a new parameter to the bonsai "module" that would control where the download is done would help here? Then the playbook authors could instruct ansible that the target node should download the data from the bonsai instead of the control node?

[michaeldeaton]

Hey

thank you for that. that explains my issue the. I’ve spent all day on this. Documentation should probably have said something. I do like your suggestion though an option to choose where the download goes would be good.

Thanks

michael