Install Postman

[jelaiw]

Notes

• https://www.tecmint.com/install-postman-on-linux-desktop/
• https://www.tecmint.com/install-snap-in-linux/
• https://docs.ansible.com/ansible/latest/collections/community/general/snap_module.html

[jelaiw]

$ snap warnings
last-occurrence:  today at 15:57 UTC
warning: |
  the snapd.apparmor service is disabled; snap applications will likely not start.
  Run "systemctl enable --now snapd.apparmor" to correct this.
WARNING: There is 1 new warning. See 'snap warnings'.

Note the warning, but appears to not affect running Postman.

[jelaiw]

$ snap version 
snap    2.59.5-1
snapd   2.59.5-1
series  16
kali    2023.2
kernel  6.3.0-kali1-cloud-amd64
WARNING: There is 1 new warning. See 'snap warnings'.

[jelaiw]

Snippet from Ansible playbook.

TASK [Install Postman] ********************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible_collections.community.general.plugins.module_utils.mh.exceptions.ModuleHelperException
fatal: [kali]: FAILED! => {"changed": false, "channel": null, "classic": false, "cmd": "['state', 'classic', 'channel', 'dangerous', 'postman']", "msg": "Ooops! Snap installation failed while executing '['state', 'classic', 'channel', 'dangerous', 'postman']', please examine logs and error output for more details.", "output": {"channel": null, "classic": false, "cmd": "['state', 'classic', 'channel', 'dangerous', 'postman']", "snap_names": ["postman"], "snaps_installed": ["postman"]}, "snap_names": ["postman"], "snaps_installed": ["postman"], "vars": {"channel": null, "classic": false, "cmd": "['state', 'classic', 'channel', 'dangerous', 'postman']", "snap_names": ["postman"], "snaps_installed": ["postman"]}}

Error message seems to show that Postman snap install failed, but Postman still runs so ...

Did an experiment using snap to uninstall and reinstall postman snap, which did not throw an error.

Unclear why this is happening, for now, simply documenting this behavior here in case we want to pick it up in the future.

[jelaiw]

Doh. Need to address warning after all.

$ postman
missing profile snap-update-ns.postman.
Please make sure that the snapd.apparmor service is enabled and started
snap-update-ns failed with code 1

Postman would not start after reboot.

Possibly related to failure of "install postman" step of Ansible playbook. Perhaps no need to revisit with suggested -vvv and just address the systemctl warning.

[jelaiw]

Duh. :-D