fix: add the permissions neeed by monitor_runner.sh

[rk295]

Description

Closes #1353.

Add the ec2:DescribeTags permission needed by the monitor_runner.sh script.

Migrations required

No, although users who have potentially worked around this bug would be wise to remove their workarounds and let the module handle this.

Verification

Built a fleeting rig and observed the monitor_runner.sh script does not exit with permission denied when listing the tags.

[github-actions]

Hey @rk295! 👋

Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

• the problem being solved
• the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE.

The following ChatOps commands are supported:

• /help: notifies a maintainer to help you out

Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command.

This message was generated automatically. You are welcome to improve it.

[rk295]

From a new user experience pov it would save compute resources and time if the PR title linter reported all problems in one run, rather than reporting about one at a time.

I'm not sure if that's something the tool supports that could be fixed in the CI in this project or would require upstream to add support but it would definitely save wasting resources and produce a nicer user experience.

[kayman-mk]

From a new user experience pov it would save compute resources and time if the PR title linter reported all problems in one run, rather than reporting about one at a time.

I'm not sure if that's something the tool supports that could be fixed in the CI in this project or would require upstream to add support but it would definitely save wasting resources and produce a nicer user experience.

Absolutely. I check the documentation of the action but didn't found any setting. Could you please create an issue here?

[kayman-mk]

Looks good to me. But need a link to this monitoring script.

[rk295]

The monitoring script is here in the gitlab-runner.tftpl file. Line 19 of the script, line 339 of the template.

[rk295]

From a new user experience pov it would save compute resources and time if the PR title linter reported all problems in one run, rather than reporting about one at a time.
I'm not sure if that's something the tool supports that could be fixed in the CI in this project or would require upstream to add support but it would definitely save wasting resources and produce a nicer user experience.

Absolutely. I check the documentation of the action but didn't found any setting. Could you please create an issue here?

Will do, thanks for checking the docs!