square-coat-62279
12/29/2021, 3:50 AMable-honey-93860
12/29/2021, 4:30 AMbumpy-agent-19616
12/29/2021, 8:29 AMerror: an unhandled error occurred: Problem executing program (could not run language executor): fork/exec /usr/local/bin/node: argument list too long
during pulumi up
? We have stacks for test, stage and prod of which pulumi up
works with no problem in stage and prod environments but it doesn't in test and test stack in turn hosts environments like test01, test02, test03, test04 and test05.echoing-activity-32278
12/29/2021, 9:06 AMechoing-activity-32278
12/29/2021, 10:24 AMhappy-gpu-24908
12/29/2021, 11:39 AMpulumi up
everything works fine. But when I run pulumi refresh
I get an error error: could not load plugin for docker provider 'urn:pulumi:dev::testing::pulumi:providers:docker::example-service_docker_provider': no resource plugin 'docker' found in the workspace or on your $PATH
. What could be the reason? I get the same error when I run pulumi up --refresh
.echoing-activity-32278
12/29/2021, 1:25 PMpurple-megabyte-83002
12/29/2021, 2:06 PMpulumi
local on CI/CD pipeline ? it’s not finding my stackechoing-activity-32278
12/29/2021, 4:12 PMhundreds-painter-6367
12/29/2021, 5:28 PMaws-native:opensearchservice:Domain (merqueo-dev-search):
error: resource partially created but read failed. read error: reading resource state: operation error CloudControl: GetResource, https response error StatusCode: 400, RequestID: 5dad3d54-4208-49c1-8d6d-5bcb49ffd70f, ResourceNotFoundException: AWS::OpenSearchService::Domain Handler returned status FAILED: Resource of type 'AWS::OpenSearchService::Domain' with identifier 'merqueo-dev-search' was not found. (HandlerErrorCode: NotFound, RequestToken: 3fe72f59-101b-4656-0dad-b9fe51ed0247), create error: operation CREATE failed with "InternalFailure": Internal Failure
some-honey-3067
12/29/2021, 7:40 PM-------------------------------------------------------------------------------
NGINX Ingress controller
Release: v0.44.0
Build: f802554ccfadf828f7eb6d3f9a9333686706d613
Repository: <https://github.com/kubernetes/ingress-nginx>
nginx version: nginx/1.19.6
-------------------------------------------------------------------------------
I1229 11:12:26.402166 7 flags.go:208] "Watching for Ingress" class="nginx"
W1229 11:12:26.402595 7 flags.go:213] Ingresses with an empty class will also be processed by this Ingress controller
W1229 11:12:26.403000 7 client_config.go:614] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
W1229 11:12:26.403049 7 client_config.go:619] error creating inClusterConfig, falling back to default config: open /var/run/secrets/kubernetes.io/serviceaccount/token: permission denied
F1229 11:12:26.403200 7 main.go:299] Error while initiating a connection to the Kubernetes API server. This could mean the cluster is misconfigured (e.g. it has invalid API server certificates or Service Accounts configuration). Reason: open /var/run/secrets/kubernetes.io/serviceaccount/token: permission denied
Refer to the troubleshooting guide for more information: <https://kubernetes.github.io/ingress-nginx/troubleshooting/>
goroutine 1 [running]:
<http://k8s.io/klog/v2.stacks(0xc000128001|k8s.io/klog/v2.stacks(0xc000128001>, 0xc0003ec000, 0x1b4, 0x1d3)
<http://k8s.io/klog/v2@v2.4.0/klog.go:1026|k8s.io/klog/v2@v2.4.0/klog.go:1026> +0xb9
<http://k8s.io/klog/v2.(*loggingT).output|k8s.io/klog/v2.(*loggingT).output>(0x26915e0, 0xc000000003, 0x0, 0x0, 0xc0000a8cb0, 0x25e6c33, 0x7, 0x12b, 0x0)
<http://k8s.io/klog/v2@v2.4.0/klog.go:975|k8s.io/klog/v2@v2.4.0/klog.go:975> +0x19b
<http://k8s.io/klog/v2.(*loggingT).printf(0x26915e0|k8s.io/klog/v2.(*loggingT).printf(0x26915e0>, 0xc000000003, 0x0, 0x0, 0x0, 0x0, 0x1a92308, 0x13f, 0xc00006c190, 0x1, ...)
<http://k8s.io/klog/v2@v2.4.0/klog.go:750|k8s.io/klog/v2@v2.4.0/klog.go:750> +0x191
<http://k8s.io/klog/v2.Fatalf(...)|k8s.io/klog/v2.Fatalf(...)>
<http://k8s.io/klog/v2@v2.4.0/klog.go:1502|k8s.io/klog/v2@v2.4.0/klog.go:1502>
main.handleFatalInitError(...)
<http://k8s.io/ingress-nginx/cmd/nginx/main.go:299|k8s.io/ingress-nginx/cmd/nginx/main.go:299>
main.main()
<http://k8s.io/ingress-nginx/cmd/nginx/main.go:78|k8s.io/ingress-nginx/cmd/nginx/main.go:78> +0x3f4
goroutine 18 [chan receive]:
<http://k8s.io/klog/v2.(*loggingT).flushDaemon(0x26915e0)|k8s.io/klog/v2.(*loggingT).flushDaemon(0x26915e0)>
<http://k8s.io/klog/v2@v2.4.0/klog.go:1169|k8s.io/klog/v2@v2.4.0/klog.go:1169> +0x8b
created by <http://k8s.io/klog/v2.init.0|k8s.io/klog/v2.init.0>
<http://k8s.io/klog/v2@v2.4.0/klog.go:417|k8s.io/klog/v2@v2.4.0/klog.go:417> +0xdf
pulumi about
CLI
Version 3.20.0
Go Version go1.17.5
Go Compiler gc
Plugins
NAME VERSION
aws 4.32.0
aws 4.32.0
docker 3.1.0
eks 0.36.0
kubernetes 3.12.1
nodejs unknown
Host
OS darwin
Version 12.0.1
Arch arm64
This project is written in nodejs (/usr/local/bin/node v14.16.0)
Current Stack: my-org/db1b158c-e815-11ea-97ef-13e6b152ce19
Found no resources associated with my-org/db1b158c-e815-11ea-97ef-13e6b152ce19
Found no pending operations associated with my-org/db1b158c-e815-11ea-97ef-13e6b152ce19
Backend
Name <http://pulumi.com|pulumi.com>
URL <https://app.pulumi.com/my-user>
User my-user
NAME VERSION
@pulumi/awsx 0.32.0
@pulumi/docker 3.1.0
@pulumi/eks 0.36.0
@pulumi/kubernetes 3.12.1
@pulumi/pulumi 3.20.0
@types/node 17.0.0
@pulumi/aws 4.32.0
See my code here: https://gist.github.com/leshibily/13281cf86efc79cdb6cb80e1d24af22fabundant-yacht-50678
12/29/2021, 11:54 PMgcp:sql:DatabaseInstance (app-db):
error: gcp:sql/databaseInstance:DatabaseInstance resource 'app-db' has a problem: AtLeastOne: "settings": one of `clone,settings` must be specified. Examine values at 'DatabaseInstance.Settings'.
error: gcp:sql/databaseInstance:DatabaseInstance resource 'app-db' has a problem: AtLeastOne: "clone": one of `clone,settings` must be specified. Examine values at 'DatabaseInstance.Clone'.
error: one or more inputs failed to validate
Any ideas on how I resolve this?rhythmic-lamp-79430
12/30/2021, 4:01 AMresource_vpc = aws.ec2.Vpc(
resource_name=vars['vpc_name'],
cidr_block=vars['cidr'],
enable_classiclink_dns_support=True,
enable_dns_hostnames=True,
assign_generated_ipv6_cidr_block=True,
tags={
"Name": vars['vpc_name'],
}
)
and then would like to use the resource_vpc.ipv6_cidr_block
attribute to assign IPv6 CIDRs to subnets.
However, the representation of this attribute is required as string to the network IPNetwork function I am using to create IPv6 Subnets…
Any idea how I can obtain the string value? Thanks in advanceechoing-activity-32278
12/30/2021, 9:47 AMechoing-activity-32278
12/30/2021, 11:12 AMpulumi up
?nice-beard-3866
12/30/2021, 11:45 AM<azblob://pulumi-state>
all projects live in the same container and I name the stacks <project-name>.<stack-name>
because of the limitations, a solution taken from here
I've tried some different forms <project-name>/<project-name>.<stack-name>
, <project-name>-<project-name>.<stack-name>
, <project-name>.<stack-name>
but nothing seems to work
Any suggestions for how to reference another stack?rhythmic-lamp-79430
12/30/2021, 4:33 PMvpc_info = aws.ec2.get_vpc(id=resource_vpc.id, opts=ResourceOptions(depends_on=[resource_vpc]))
to get the ipv6 subnet…
however, if i run the whole stack in one go it fails…
if i run it in stages i.e. create just the vpc and then create the subnet in second try it works fine.
i have tried the depends_on mechanism but doesnt seem to be working…
any idea what I might be doing wrong?most-lighter-95902
12/30/2021, 11:26 PMawsx.ecr.buildAndPushImage
is calling the wrong ECR repo (i.e. the failed push error log shows the wrong aws account ID)most-lighter-95902
12/30/2021, 11:26 PMmost-lighter-95902
12/30/2021, 11:35 PMawait aws.getCallerIdentity({})
, I get the right aws account - so aws is obviously correctly configured - this is strangemost-lighter-95902
12/30/2021, 11:40 PMconst apiImage = awsx.ecr.buildAndPushImage(`api-image`, {
context: projectRootPath,
dockerfile: './Dockerfile.dev',
})
careful-vase-44898
12/30/2021, 11:55 PMProperties
attribute don't trigger a state change, so subsequent calls to pulumi up
don't pick up my changes. As an experiment I added a value to the Tags
property, and that was picked up just fine. Any idea what might be happening?rhythmic-lamp-79430
12/31/2021, 2:58 AMechoing-activity-32278
12/31/2021, 3:36 AMpulumi up
after hitting showing the details
option.mammoth-airline-91759
12/31/2021, 6:13 AMbillions-lawyer-5518
12/31/2021, 10:17 AMquick-wolf-8403
12/31/2021, 5:34 PMfixCachingVCL, err := fastly.NewServiceDynamicSnippetContentv1(ctx, "X-Http-Method-Override",
&fastly.ServiceDynamicSnippetContentv1Args{
Content: pulumi.String("unset req.http.X-Http-Method-Override;"),
ServiceId: bitmovincdn.ID(),
SnippetId: , // Need a real one. manual?
})
most-lighter-95902
12/31/2021, 8:09 PMawsx.ecr.buildAndPushImage
), does it run the build command locally? I’m asking because I keep getting The build failed because the process exited too early. This probably means the system ran out of memory
late-energy-66663
01/01/2022, 6:18 PMLocalWorkspace
. This implementation relies on Pulumi.yaml and Pulumi.<stack>.yaml as the intermediate format for Project and Stack settings. Modifying ProjectSettings will alter the Workspace Pulumi.yaml file, and setting config on a Stack will modify the Pulumi.<stack>.yaml file. This is identical to the behavior of Pulumi CLI driven workspaces. Custom Workspace implementations can be used to store Project and Stack settings as well as Config in a different format, such as an in-memory data structure, a shared persistent SQL database, or cloud object storage. Regardless of the backing Workspace implementation,
https://pkg.go.dev/github.com/pulumi/pulumi/sdk/v3/go/auto@v3.19.0#NewLocalWorkspaceable-honey-93860
01/01/2022, 8:32 PMgroups_includeds
vs groups_included
which the terraform provider shows the latter.
groups_included = “${<http://data.okta_group.everyone.id|data.okta_group.everyone.id>}”
so I assume there was either a typo for the $
or the converter didn't accurately handled it.
This mishandled conversion causes the documentation to mislead the user into thinking group names and/or id’s can be used but ultimately only group id’s are applicable.able-honey-93860
01/01/2022, 8:32 PMgroups_includeds
vs groups_included
which the terraform provider shows the latter.
groups_included = “${<http://data.okta_group.everyone.id|data.okta_group.everyone.id>}”
so I assume there was either a typo for the $
or the converter didn't accurately handled it.
This mishandled conversion causes the documentation to mislead the user into thinking group names and/or id’s can be used but ultimately only group id’s are applicable.billowy-army-68599
01/01/2022, 11:44 PMable-honey-93860
01/01/2022, 11:48 PMbillowy-army-68599
01/01/2022, 11:51 PMable-honey-93860
01/01/2022, 11:54 PM