clever-cartoon-41433
03/07/2021, 8:37 PMsticky-match-71841
03/08/2021, 10:10 AMpulumi up --tracing trace.trace -v 10
Previewing update (<redacted>)
View Live: <redacted>.
Sometimes a preview takes 20 minutes to complete, where it recently only took a couple of minutes. Been trying to debug this for a few weeks now, but i have been unable to figure out what causes thischilly-analyst-14900
03/08/2021, 11:28 AMchilly-analyst-14900
03/08/2021, 11:29 AM"sku": {
"name": "Standard",
"family": "C",
"capacity": 1
}
Pulumi using Azure Native:
public sealed class SkuArgs : Pulumi.ResourceArgs
{
/// <summary>
/// The size of the RedisEnterprise cluster. Defaults to 2 or 3 depending on SKU. Valid values are (2, 4, 6, ...) for Enterprise SKUs and (3, 9, 15, ...) for Flash SKUs.
/// </summary>
[Input("capacity")]
public Input<int>? Capacity { get; set; }
/// <summary>
/// The type of RedisEnterprise cluster to deploy. Possible values: (Enterprise_E10, EnterpriseFlash_F300 etc.)
/// </summary>
[Input("name", required: true)]
public InputUnion<string, Pulumi.AzureNative.Cache.SkuName> Name { get; set; } = null!;
public SkuArgs()
{
}
}
chilly-analyst-14900
03/08/2021, 11:34 AMclever-lawyer-94920
03/08/2021, 1:05 PM<http://dkr.ecr.ap-south-1.amazonaws.com/microservices-064ef0a|dkr.ecr.ap-south-1.amazonaws.com/microservices-064ef0a>
Is there a way to avoid this?clever-plumber-29709
03/08/2021, 8:30 PM:latest
as is stated in multiples sites, is not a best practice.
So the CD system, tags an specific version and pushes it to ecr.
Then i want to run pulumi to setup all infra. including the task definition, so pulumi needs to define the container image and tag, at this point.
So the problem is that i'm not sure how pulumi will now what is the specific tag it needs to use for the task definition.
I first thought of getting the repo info, and getting the latest image from it, but seems like the ecr resources, only allow me to get, the specific repo info, or and specific image info (so i have to ask for an specific tag, which pulumi does not know)
I could still do this via boto or aws cli, using list-images and parsing the output to get the latest tag, but i'm wondering if this is the best approach, if i should just use :latest
and force a deploy, when pulumi runs. if if there are other options, or ideas i'm overseeingloud-battery-37784
03/08/2021, 8:43 PMloud-battery-37784
03/08/2021, 8:46 PMshy-oxygen-8874
03/08/2021, 11:36 PM* missing required configuration key "aws:region": The region where AWS operations will take place. Examples are us-east-1, us-west-2, etc.
Set a value using the command `pulumi config set aws:region <value>`.
When I check my pulumi config, I have that set:
>pulumi config
KEY VALUE
aws:region us-west-2
I'm on 2.18.0, is this a known issue or am I doing something wrong?adorable-musician-67025
03/09/2021, 10:24 AMworried-knife-31967
03/09/2021, 12:37 PMbitter-river-54082
03/09/2021, 12:53 PMnew aws.iam.ServiceLinkedRole("analyticsdb", {
awsServiceName: "<http://rds.amazonaws.com|rds.amazonaws.com>",
})
Everything is ok as long as this is the first (or only) deployment in the specific AWS account, but if I do few deployments on the same account all deployments after the first one will fail, because I cannot have more than one RDS service linked role. How should I solve this kind of issue?flat-insurance-25294
03/09/2021, 12:55 PMflat-insurance-25294
03/09/2021, 12:56 PMconst privateKey = Config.getOrCreateSecret("my_secret", private_key)
flat-insurance-25294
03/09/2021, 1:00 PMpulimi.secret(value)
what do I use to fetch it with config.getSecret(---?)
?worried-knife-31967
03/09/2021, 1:15 PMacceptable-stone-35112
03/09/2021, 1:19 PMflat-insurance-25294
03/09/2021, 1:26 PMNote: All attributes including the generated password will be stored in the raw state as plain-text. Read more about sensitive data in state.in https://www.pulumi.com/docs/reference/pkg/random/randompassword/ This wasn’t there before, so what is the best approach now to generate a password that isn’t in cleartext? We use this to generate password for RDS.
bulky-continent-73012
03/09/2021, 1:43 PMacceptable-stone-35112
03/09/2021, 2:20 PMacceptable-forest-23292
03/09/2021, 2:24 PM- name: Select Staging Stack
uses: <docker://pulumi/actions>
with:
args: stack select staging
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
PULUMI_ROOT: ${{ env.PULUMI_ROOT }}
but when i run it it returns me this error
error: no Pulumi.yaml project file found (searching upwards from /github/workspace). If you have not created a project yet, use `pulumi new` to do so
I understand that the workflow can’t find the pulumi folder but I have set the variable env.PULUMI_ROOT
to point to where the project is PULUMI_ROOT: apps/.pulumi
am I missing something?boundless-airport-99052
03/09/2021, 2:51 PMworried-knife-31967
03/09/2021, 3:17 PMbroad-dog-22463
03/09/2021, 3:24 PMclever-cartoon-41433
03/09/2021, 9:46 PMconfigured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
clever-cartoon-41433
03/09/2021, 9:46 PMcurved-pharmacist-41509
03/10/2021, 3:21 AMup
doesn’t run code which is checking for isDryMode()
clever-cartoon-41433
03/10/2021, 4:45 AMbulky-continent-73012
03/10/2021, 9:18 AMaccure1/xxxxxx-xxxxx/dev (pulumi:pulumi:Stack)
error: update failed
xxxxxx-eks-cluster (aws:eks:Cluster)
error: 1 error occurred:
* creating urn:pulumi:dev::xxxxx-xxxxx::aws:eks/cluster:Cluster::xxxxx-eks-cluster: 1 error occurred:
* AccessDeniedException:
status code: 403, request id: 4d642e75-03cc-4a60-ab0d-34911e23a39f
When i looked at the CloudTrail i see no error code. So all resources are created.
Moreover, the error indicate creating "urn😛ulumi:dev". Could you pls help me to remove this error
I also can not destroy the created resources:
pulumi:pulumi:Stack (xxxxx-xxxxxx-dev):
error: update failed
aws:eks:Cluster (xxxxxx-eks-cluster):
error: deleting urn:pulumi:dev::xxxxx-xxxx::aws:eks/cluster:Cluster::xxxxx-eks-cluster: 1 error occurred:
* error waiting for EKS Cluster (xxxxxxx-eks-cluster-c0130d5) deletion: AccessDeniedException:
status code: 403, request id: f81c9336-3a10-40d2-8c2a-fbc76018ce6f
bulky-continent-73012
03/10/2021, 9:18 AMaccure1/xxxxxx-xxxxx/dev (pulumi:pulumi:Stack)
error: update failed
xxxxxx-eks-cluster (aws:eks:Cluster)
error: 1 error occurred:
* creating urn:pulumi:dev::xxxxx-xxxxx::aws:eks/cluster:Cluster::xxxxx-eks-cluster: 1 error occurred:
* AccessDeniedException:
status code: 403, request id: 4d642e75-03cc-4a60-ab0d-34911e23a39f
When i looked at the CloudTrail i see no error code. So all resources are created.
Moreover, the error indicate creating "urn😛ulumi:dev". Could you pls help me to remove this error
I also can not destroy the created resources:
pulumi:pulumi:Stack (xxxxx-xxxxxx-dev):
error: update failed
aws:eks:Cluster (xxxxxx-eks-cluster):
error: deleting urn:pulumi:dev::xxxxx-xxxx::aws:eks/cluster:Cluster::xxxxx-eks-cluster: 1 error occurred:
* error waiting for EKS Cluster (xxxxxxx-eks-cluster-c0130d5) deletion: AccessDeniedException:
status code: 403, request id: f81c9336-3a10-40d2-8c2a-fbc76018ce6f
microscopic-dress-1605
03/10/2021, 10:19 AMbrave-planet-10645
03/10/2021, 10:25 AM