freezing-umbrella-5483
05/11/2022, 3:48 PMmagnificent-scientist-71902
05/11/2022, 4:52 PMglamorous-holiday-25694
05/11/2022, 5:37 PMEKS
. No matter what changes I add (a new node group or simply adding a Helm chart) an EKS cluster replace
is always included in the changes.
Is there something obvious Im missing?
Thank you!refined-evening-26861
05/12/2022, 6:31 AMrefined-evening-26861
05/12/2022, 6:41 AMbulky-agent-73210
05/12/2022, 7:30 AMquick-quill-70949
05/12/2022, 10:52 AMwet-fall-68417
05/12/2022, 11:23 AMerror creating API Gateway v2 route: ConflictException: Route with key $connect already exists for this API
The problem is when i create the aws.apigatewayv2.Api
resource, The $connect route creates automatically.
The only way to create an integration request to a route, is to create the aws.apigatewayv2.Route
resource in pulumi, and set the integration resource in it.
But again, i can’t create the route, because it is already exist.
const exampleApi = new aws.apigatewayv2.Api("exampleApi", {protocolType: "WEBSOCKET"});
const exampleIntegration = new aws.apigatewayv2.Integration("exampleIntegration", {
apiId: exampleApi.id,
integrationType: "HTTP_PROXY",
integrationMethod: "ANY",
integrationUri: "<https://example.com/{proxy}>",
});
const exampleRoute = new aws.apigatewayv2.Route("exampleRoute", {
apiId: exampleApi.id,
routeKey: "$connect",
target: pulumi.interpolate`integrations/${exampleIntegration.id}`,
});
me and @purple-answer-54279 looking for answers for a long time without any feedback! last time @great-queen-39697 managed to help us.
How can we solve it?microscopic-cpu-38113
05/12/2022, 12:12 PMagreeable-king-2755
05/12/2022, 12:59 PMgreen-daybreak-98726
05/12/2022, 5:36 PMlively-helmet-97905
05/12/2022, 7:22 PMgetting credentials: exec plugin is configured to use API version <http://client.authentication.k8s.io/v1beta1|client.authentication.k8s.io/v1beta1>, plugin returned version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>
Any walkaround of how to solve this ?creamy-fall-88031
05/12/2022, 8:14 PM{
frontendIPConfiguration: {
id: pulumi.all([subscriptionId, resourceGroup.name])
.apply(([subscription, resourceGroup]) => `/subscriptions/${subscription}/resourceGroups/${resourceGroup}/providers/Microsoft.Network/applicationGateways/appgw/frontendIPConfigurations/appgwfip`)
},
frontendPort: {
id: pulumi.all([subscriptionId, resourceGroup.name])
.apply(([subscription, resourceGroup]) => `/subscriptions/${subscription}/resourceGroups/${resourceGroup}/providers/Microsoft.Network/applicationGateways/appgw/frontendPorts/appgwfp80`)
},
name: `appgwhttplistener-${environmentLabel}`,
protocol: "Http",
},
average-tiger-58107
05/12/2022, 11:38 PMSecret
resource from @pulumi/aws/secretsmanager/secret
and seems to expect one from @pulumi/aws/ecs/container
according to the error message in my editor (attached).
----
The problem I'm having is that I cant find this resource anywhere in docs or code. Any ideas?billions-tiger-23195
05/13/2022, 1:04 AMpolite-king-94596
05/13/2022, 1:07 AMstrong-intern-84363
05/13/2022, 1:51 AMadamant-minister-95586
05/13/2022, 2:38 AMKubeconfig user entry is using deprecated API version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>. Run 'aws eks update-kubeconfig' to update.
error: exec plugin: invalid apiVersion "<http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>"
error: update failed
I was attempting to locate my kubeconfig but theres no config file or directory in ~./kube
so now I'm stuckancient-nightfall-54764
05/13/2022, 7:47 AMif (stackName === "development") {
import "vpc-development"
} else if (stackName === "staging") {
import vpc-staging
}
kind-needle-67381
05/13/2022, 8:30 AMstack = auto.create_or_select_stack(stack_name="core-redis-relay-5" , program=common.create_relay , work_dir="buildlib/infra-python")
stack.up(on_output=print)
kind-needle-67381
05/13/2022, 8:31 AMcreate_relay
I do pulumi.log / print but I can't see their output ? How can I select the log level with automation ? how can I see my prints ?great-sunset-355
05/13/2022, 8:53 AMCodePathOptions
it took me 3 hours and various github issues to land on that page?
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/closure/#CodePathOptionsbland-lamp-16797
05/13/2022, 10:37 AMpolite-king-94596
05/13/2022, 2:21 PMtaskdef = new cdk.ecs.FargateTaskDefinition(...)
ecs = new awsx.ecs.FargateService({
taskDefinition: taskdef,
...
})
microscopic-flower-5848
05/13/2022, 2:26 PMdamp-truck-25843
05/13/2022, 2:49 PMmost-state-94104
05/13/2022, 4:37 PMRunning setup.py install for pulumi-eks ... error
ERROR: Command errored out with exit status 1:
[...]
[resource plugin eks-0.39.0] installing
Downloading plugin: 0 B / 682.52 KiB [---------------------------------] 0.00%
Downloading plugin: 682.52 KiB / 682.52 KiB [=======================] 100.00% 0s
env: node: No such file or directory
error: installing [resource plugin eks-0.39.0] from : installing plugin dependencies: exit status 127
adamant-minister-95586
05/13/2022, 7:33 PMpulumi-eks
appears to be the failing point on new installations for the v1alpha1
deprecation issue. I see there's a PR that actually fixes the problem I had yesterday https://github.com/pulumi/pulumi-eks/pull/701/commits
I'm pretty new to Pulumi but was wondering what a PR merge schedule looks like for these packages. I'm currently building the package myself and installing it for now but would like to have the officially built package installed instead. I hope this message doesn't come off as rude cause I know everyone's busy 😅 but I'm so far enjoying the experience with Pulumi 🙂brave-lizard-56518
05/13/2022, 8:52 PMfancy-spoon-46046
05/14/2022, 2:40 PM