cdk-insights 1.10.2 → 1.11.1

package/dist/analysis/static/awsServices/CloudWatch/logRetention/cloudWatchLogRetentionChecks.d.ts

@@ -1,2 +1,2 @@
-import type { AnalysisResults, CloudFormationStack, CreateFindingFunction } from '../../../../../types/analysis.types';
-export declare const checkCloudWatchLogRetention: (template: CloudFormationStack, createFinding: CreateFindingFunction) => AnalysisResults;
+import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, RuleContext } from '../../../../../types/analysis.types';
+export declare const checkCloudWatchLogRetention: (template: CloudFormationStack, createFinding: CreateFindingFunction, ruleContext?: RuleContext) => AnalysisResults;

package/dist/analysis/static/awsServices/CloudWatch/logRetention/cloudWatchLogRetentionChecks.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/analysis/static/awsServices/IAM/iamPolicies.d.ts

@@ -1,2 +1,11 @@
-import type { AnalysisResults, CloudFormationStack, CreateFindingFunction } from '../../../../types/analysis.types';
-export declare const checkIamPolicies: (template: CloudFormationStack, createFinding: CreateFindingFunction) => AnalysisResults;
+import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, RuleContext } from '../../../../types/analysis.types';
+/**
+ * IAM policies created by L3 patterns (AWS Solutions Constructs, cdk-monitoring,
+ * etc.) frequently contain wildcards because the pattern's purpose is to wire
+ * up sensible permissions for a multi-resource workload. A user fixing this at
+ * the CFN-resource level usually means escape-hatching the pattern. Severity
+ * stays Security-relevant but is downgraded so CI doesn't gate on what the
+ * user can't fix without breaking the pattern. Remediation redirects to the
+ * pattern's own props.
+ */
+export declare const checkIamPolicies: (template: CloudFormationStack, createFinding: CreateFindingFunction, ruleContext?: RuleContext) => AnalysisResults;

package/dist/analysis/static/awsServices/Lambda/dlq/lambdaDlqChecks.d.ts

@@ -1,2 +1,2 @@
-import type { AnalysisResults, CloudFormationStack, CreateFindingFunction } from '../../../../../types/analysis.types';
-export declare const checkLambdaDeadLetterQueue: (template: CloudFormationStack, createFinding: CreateFindingFunction) => AnalysisResults;
+import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, RuleContext } from '../../../../../types/analysis.types';
+export declare const checkLambdaDeadLetterQueue: (template: CloudFormationStack, createFinding: CreateFindingFunction, ruleContext?: RuleContext) => AnalysisResults;

package/dist/analysis/static/awsServices/S3/buckets/bucketChecks.d.ts

@@ -1,2 +1,2 @@
-import type { AnalysisResults, CloudFormationStack, CreateFindingFunction } from '../../../../../types/analysis.types';
-export declare const checkS3Buckets: (template: CloudFormationStack, createFinding: CreateFindingFunction) => AnalysisResults;
+import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, RuleContext } from '../../../../../types/analysis.types';
+export declare const checkS3Buckets: (template: CloudFormationStack, createFinding: CreateFindingFunction, ruleContext?: RuleContext) => AnalysisResults;

package/dist/analysis/static/staticAnalysis.d.ts

@@ -1,5 +1,5 @@
 import type { CustomRuleDefinition } from '../../rules/customRules.types';
-import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, ServiceName, Severity } from '../../types/analysis.types';
+import type { AnalysisResults, CloudFormationStack, CreateFindingFunction, RuleContext, ServiceName, Severity } from '../../types/analysis.types';
 import type { ConstructMetadata } from './solutionConstructs/loadConstructMetadata';
 export type AnalysisStatistics = {
     totalResources: number;
@@ -22,12 +22,18 @@ export type StaticAnalysisOptions = {
     includeStatistics?: boolean;
     /** User-defined custom rules to evaluate */
     customRules?: CustomRuleDefinition[];
+    /**
+     * Optional context passed to rules that opt in. Lets rules adapt
+     * their behaviour based on construct level (L1/L2/L3) and the user's
+     * cdk.json feature flags. Rules that don't use it work unchanged.
+     */
+    ruleContext?: RuleContext;
 };
 export type StaticAnalysisResultWithStats = {
     findings: AnalysisResults;
     statistics: AnalysisStatistics;
 };
-export declare const runStaticAnalysis: (cloudformationTemplate: CloudFormationStack, createFinding: CreateFindingFunction, selectedServices?: ServiceName[], solutionsRegistry?: Record<string, ConstructMetadata>, customRules?: CustomRuleDefinition[]) => AnalysisResults;
+export declare const runStaticAnalysis: (cloudformationTemplate: CloudFormationStack, createFinding: CreateFindingFunction, selectedServices?: ServiceName[], solutionsRegistry?: Record<string, ConstructMetadata>, customRules?: CustomRuleDefinition[], ruleContext?: RuleContext) => AnalysisResults;
 export declare const runStaticAnalysisWithOptions: (cloudformationTemplate: CloudFormationStack, createFinding: CreateFindingFunction, options?: StaticAnalysisOptions) => StaticAnalysisResultWithStats;
 export type BatchAnalysisResult = {
     results: Record<string, AnalysisResults>;