Update rule metadata (#456)

Co-authored-by: Seppli11 <9285506+Seppli11@users.noreply.github.com>
GitOrigin-RevId: 085e34b46eece4b3de59c366946fad9b71eb8eae

Author: 2 people

python-checks/src/main/resources/org/sonar/l10n/py/rules/python/S7609.html

@@ -1,4 +1,4 @@
-<p>This rule raises and issue when AWS CloudWatch <code>put_metric_data</code> namespace begins with <code>AWS/</code></p>
+<p>This rule raises an issue when AWS CloudWatch <code>put_metric_data</code> namespace begins with <code>AWS/</code></p>
 <h2>Why is this an issue?</h2>
 <p>AWS CloudWatch has reserved namespaces that begin with 'AWS/' for its own internal services and metrics. These namespaces are used by AWS to
 publish official service metrics such as EC2 instance metrics, Lambda function metrics, S3 bucket metrics, and others. When you attempt to publish
@@ -7,8 +7,8 @@ <h2>Why is this an issue?</h2>
 <h3>What is the potential impact?</h3>
 <p>Using AWS service namespaces can lead to metric publishing failures, data corruption, or unexpected behavior in CloudWatch dashboards. It may also
 cause confusion between your custom metrics and official AWS service metrics, making monitoring and troubleshooting more difficult. Additionally, AWS
-may reject such metric publications or they may interfere with existing service metrics.</p>
-<h2>How to fix it in boto3</h2>
+may reject such metric publications, or they may interfere with existing service metrics.</p>
+<h2>How to fix it in Boto3</h2>
 <p>Use a custom namespace that does not begin with 'AWS/' when publishing metrics with CloudWatch. Choose a meaningful namespace that reflects your
 application or service name, such as 'MyApp/', 'CustomService/', or your organization name.</p>
 <h3>Code examples</h3>
@@ -87,9 +87,9 @@ <h4>Compliant solution</h4>
 <h2>Resources</h2>
 <h3>Documentation</h3>
 <ul>
-  <li> <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricData.html">AWS CloudWatch PutMetricData API
-  Reference</a> </li>
-  <li> <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.html#Namespace">CloudWatch Concepts -
-  Namespaces</a> </li>
+  <li> AWS Documentation - <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricData.html">AWS CloudWatch
+  PutMetricData API Reference</a> </li>
+  <li> AWS Documentation - <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.html#Namespace">CloudWatch
+  Concepts - Namespaces</a> </li>
 </ul>
 

python-checks/src/main/resources/org/sonar/l10n/py/rules/python/S7609.json

@@ -6,7 +6,9 @@
     "func": "Constant\/Issue",
     "constantCost": "5min"
   },
-  "tags": [],
+  "tags": [
+    "aws"
+  ],
   "defaultSeverity": "Major",
   "ruleSpecification": "RSPEC-7609",
   "sqKey": "S7609",

python-checks/src/main/resources/org/sonar/l10n/py/rules/python/S7621.json

@@ -10,7 +10,7 @@
     "aws"
   ],
   "defaultSeverity": "Major",
-  "ruleSpecification": "RSPEC-S7621",
+  "ruleSpecification": "RSPEC-7621",
   "sqKey": "S7621",
   "scope": "Main",
   "quickfix": "infeasible",

sonarpedia.json

@@ -3,7 +3,7 @@
   "languages": [
     "PY"
   ],
-  "latest-update": "2025-08-14T09:27:55.988002910Z",
+  "latest-update": "2025-08-18T14:36:17.206114098Z",
   "options": {
     "no-language-in-filenames": true,
     "preserve-filenames": true