floci-io/floci

Service IAM AWS API Action GetPolicyVersion / GetPolicy / ListPolicyVersions (AWS-managed policies) Expected behavior Real AWS reports each managed policy's actual default version number, which reflects how many times AWS has revised that policy's document. For example, AmazonS3ReadOnlyAccess's current default version is v3 (last revised August 2023), and its earlier v1/v2 documents remain individually retrievable via GetPolicyVersion. Actual behavior Floci reports every AWS-managed policy's default version as v1, regardless of how many times AWS has actually revised it, and only ever stores the single current document. AmazonS3ReadOnlyAccess is a concrete example: floci's GetPolicy reports DefaultVersionId: v1, matching real AWS's version numbering scheme only by coincidence for policies AWS has never revised (e.g. AdministratorAccess, genuinely v1 on real AWS). For a policy AWS has revised, like AmazonS3ReadOnlyAccess, floci's reported version number simply does not match what a real

Ec2QueryHandler dispatches ten operations on main with no corresponding row in docs/services/ec2.md. Found via a programmatic reconciliation of the handler's action switch against the docs table while working on feature/ec2 (PR #2596); confirmed still true against current upstream/main. All ten work correctly — this is a documentation gap only, no behavior defect. The gap Operation Area AttachVolume Volumes DetachVolume Volumes DescribeSnapshots Volumes / snapshots CreateFlowLogs Flow logs DeleteFlowLogs Flow logs DescribeFlowLogs Flow logs RequestSpotInstances Spot DescribeSpotInstanceRequests Spot CancelSpotInstanceRequests Spot DescribeVpnGateways VPN gateways Reproduce: git show upstream/main:src/main/java/io/github/hectorvent/floci/services/ec2/Ec2QueryHandler.java — diff the case "..." -> labels against the | Action | rows in docs/services/ec2.md. Why this is separate from #2596 feature/ec2 (#2596) documents the 29 operations it introduces itself

What's wrong Three services registered in ResolvedServiceCatalog have no row in the service matrix at docs/services/index.md: controltower mwaa cloudcontrol ResolvedServiceCatalog holds 79 ServiceDescriptor entries, 77 of them with includeInStatus=true. The matrix in docs/services/index.md has 77 rows, but six of those are sub-rows pointing at an already-listed page (DynamoDB Streams → dynamodb.md#streams, API Gateway v2 → api-gateway.md#v2, CloudWatch Metrics → cloudwatch.md#metrics, SES v2 → ses.md#v2, AppConfigData → appconfig.md#data-plane, IoT Data → iot.md), so it enumerates 71 distinct services. The prose count of 71 appears in docs/services/index.md:3, docs/index.md:15, docs/index.md:115 and README.md:181. It is internally consistent with the matrix, but it undercounts what the emulator actually serves. The truthful figure is 74. Why it matters ControlTowerService is live: it is registered in the catalog, controltower reports in the health endpoint, and docs/servi

Raspberry PI model 4B does not have LSE causing it to be restarted again and again in docker or fail to start in the installed application. Provide a 8.0 version of the package