import * as r53r from "@distilled.cloud/aws/route53resolver";
import * as Effect from "effect/Effect";
import * as Layer from "effect/Layer";
import * as AWSBindings from "../AWSBindings.ts";
import { ListResolverRuleAssociations } from "./ListResolverRuleAssociations.ts";
import type { ResolverRule } from "./ResolverRule.ts";
/**
* Bespoke (not via `BindingHttp.ts`): the operation is filter-based rather
* than ID-keyed, so the rule is injected as a `ResolverRuleId` filter instead
* of a request field. The IAM grant is `Resource: "*"` — verified live:
* `route53resolver:ListResolverRuleAssociations` does not support
* resource-level permissions (a rule-ARN-scoped grant is AccessDenied), the
* runtime callable's injected filter is what scopes results to the bound
* rule. The operation also internally describes the associated VPCs, so
* `ec2:DescribeVpcs` is required alongside it (also verified live — without
* it the call fails with `InvalidParameterException: You are not authorized
* to perform this operation ... ec2:DescribeVpcs`).
*/
export const ListResolverRuleAssociationsHttp = Layer.effect(
ListResolverRuleAssociations,
Effect.gen(function* () {
const bind = yield* AWSBindings.Bind;
const op = yield* AWSBindings.withCredentials(r53r.listResolverRuleAssociations);
return Effect.fn(function* (rule: ResolverRule) {
const ResolverRuleId = yield* rule.resolverRuleId;
if (!globalThis.__ALCHEMY_RUNTIME__) {
yield* bind`AWS.Route53Resolver.ListResolverRuleAssociations(${rule})`({
policyStatements: [
{
Effect: "Allow",
Action: ["route53resolver:ListResolverRuleAssociations", "ec2:DescribeVpcs"],
Resource: ["*"],
},
],
});
}
return Effect.fn(`AWS.Route53Resolver.ListResolverRuleAssociations(${rule.LogicalId})`)(
function* (request?: Omit<r53r.ListResolverRuleAssociationsRequest, "Filters">) {
return yield* op({
...request,
Filters: [{ Name: "ResolverRuleId", Values: [yield* ResolverRuleId] }],
});
},
);
});
}),
);