feat(table): add aws_rds_db_maintenance_action

[fyqtian]

Integration test logs

Logs

Add passing integration test logs here

Example query results

Results

 resource_identifier                                                                 | action        | opt_in_status | auto_applied_after_date | current_apply_date | description                                     | forced_apply_date | tags   | title                             >
+-------------------------------------------------------------------------------------+---------------+---------------+-------------------------+--------------------+-------------------------------------------------+-------------------+--------+----------------------------------->
| arn:aws:rds:us-west-2:000000000000:cluster:cluster1                                 | system-update | <null>        | <null>                  | <null>             | Upgrade to Aurora PostgreSQL 15.5.6             | <null>            | <null> | arn:aws:rds:us-west-2:000000000000>
| arn:aws:rds:us-west-2:000000000000:db:db1                                           | system-update | <null>        | <null>                  | <null>             | New Operating System patch is available         | <null>            | <null> | arn:aws:rds:us-west-2:000000000000>
| arn:aws:rds:us-west-2:000000000000:cluster:cluster1                                 | os-upgrade    | <null>        | <null>                  | <null>             | New Operating System patch is available         | <null>            | <null> | arn:aws:rds:us-west-2:000000000000>
| arn:aws:rds:us-west-2:000000000000:db:db2                                           | system-update | <null>        | <null>                  | <null>             | New Operating System patch is available         | <null>            | <null> | arn:aws:rds:us-west-2:000000000000>
| arn:aws:rds:us-west-2:000000000000:db:db3                                           | db-upgrade    | <null>        | <null>                  | <null>             | New engine patch version is available: 13.15.R3 | <null>            | <null> | arn:aws:rds:us-west-2:000000000000>
| arn:aws:rds:us-west-2:000000000000:cluster:cluster1                                 | system-update | <null>        | <null>                  | <null>             | Upgrade to Aurora PostgreSQL 14.11.4            | <null>            | <null> | arn:aws:rds:us-west-2:000000000000

[ParthaI]

Hello @fyqtian, I’ve added a few initial review comments. When you get a chance, could you please take a look?

Additionally, it would be great to include more example queries in the documentation.

[ParthaI]

Suggested change

	{
	Name: "arn",
	Description: "The Amazon Resource Name (ARN) of the resource that the pending maintenance action applies to.",
	Type: proto.ColumnType_STRING,
	Transform: transform.FromField("ResourceIdentifier"),
	},
	{
	Name: "resource_identifier",
	Description: "The ARN of the resource that has pending maintenance actions.",
	Type: proto.ColumnType_STRING,
	},

The aws_rds_db_maintenance_action table is designed to display pending actions for clusters.

As per table development standards, if maintenance_action follows a standard ARN format, we should include an ARN column. Otherwise, the column name should align with the API response.

[ParthaI]

I agree that these changes will help optimize the code and make it reusable for tables with a minimum limit of 1 per page.

I also noticed that the minimum value for this is 20. You can find more details here: AWS Documentation.

To maintain consistency across tables, could you please follow the standards used in other tables?

[ParthaI]

Suggested change

	type result struct {
	Name string
	ResourceIdentifier string
	IsCluster bool
	types.PendingMaintenanceAction
	}
	type result struct {
	ResourceIdentifier string
	types.PendingMaintenanceAction
	}

Since we don't include columns for attributes that are not directly part of the API response, it would be best to avoid adding them.

Additionally, could we move the custom struct from the function scope to the table scope? This would make it reusable for fetching hydrate data in any child tables if needed.

[ParthaI]

Please add the context cancellation logic here to ensure that if the context is canceled, the loop terminates immediately.

For example: https://github.com/turbot/steampipe-plugin-aws/blob/main/aws/table_aws_rds_db_cluster.go#L523