jhsinger-klotho
jhsinger-klotho
Current State: Instances correctly deregistered, but dont see the default namespace and services cleaned up outside of that Desired state: Want the ability to allow the controller to properly clean...
attempting to resolve #145 Implementing bellman ford algorithm for shortest path to include calculations of negative weights in a weighted graph. The bellman ford algorithm will be run in ShortestPath...
### What happened? The Target group looks like it successfully creates, but then an error message causes the entire up to fail, because it seems like it cannot read the...
this is likely because we are looking for errors in property vertex evaluation, but sometimes we dont evaluate in order so that assumption is broken. repro ``` [ { "error":...
deleted lambda -> secret and saw the following policy modification in the lambdas role. The resource just becomes empty but the policy doesnt get removed policy: pulumi.jsonStringify({Statement: [{Action: ["secretsmanager:DescribeSecret", "secretsmanager:GetSecretValue"],...
* creating ECS Task Definition (ecs_service_0): ClientException: When networkMode=awsvpc, the host ports and container ports in port mappings must match. * creating ECS Task Definition (ecs_service_0): ClientException: Invalid setting for...
this requires path selection to look at the task definitions portmappings in order to understand what to expose. Right now path selection does not take properties into consideration and just...
https://github.com/klothoplatform/klotho/blob/72953b0ceb9c005821b7dd5935b0f6dfcb505b61/pkg/engine2/operational_eval/vertex_edge.go#L46C1-L68C1 property vertices should be able to determine their speculative dependencies. The good example is the Triggers field for deployments since it needs to conditionally wait for other dependencies