icy-controller-6092
05/26/2022, 4:37 AMpulumi stack init
no longer create a new yaml file?icy-controller-6092
05/26/2022, 9:53 AMsticky-salesmen-54387
05/26/2022, 2:51 PMsparse-midnight-5337
05/26/2022, 3:17 PMconst dict = service.dictionaries.apply(d => d?.[0].dictionaryId || '1234') // <--- This always returns undefined, so default to 1234
however because of the comment above whenever i run pulumi up
i get the following error.
Diagnostics:
fastly:index:ServiceDictionaryItems (CredentialsDict):
error: 1 error occurred:
* Error creating dictionary items: service 6JGsFBzFbONzfbcXDyfRP3, dictionary 1234, 400 - Bad Request:
Title: Bad request
Detail: Couldn't find Dictionary '{ dictionary_id => 1234, service_id => 6JGsFBzFbONzfbcXDyfRP3 }'
pulumi:pulumi:Stack (fastly-shell-dev):
error: update failed
Is it possible to retrieve this ID during the deployment process? If not how can I query this after the service is deployed and still able to deploy the dictionary at the same time?billowy-area-48390
05/26/2022, 3:26 PMmost-jordan-25674
05/26/2022, 4:13 PMconfig.requireSecret('something')
I get an output…which won’t be useable in the string. Is there a better way to get these values that would be different per stack?eager-pilot-57366
05/26/2022, 5:02 PMkind-room-82948
05/26/2022, 6:06 PMrequireOutput()
from the stack reference it always ends up as Output<any>
type. Is there a way to set the expected type of the output so I can get something like pulumi.Output<string>
or other types?sticky-salesmen-54387
05/26/2022, 6:08 PMquick-wolf-8403
05/26/2022, 6:21 PMPulumi.prod.yaml
, before I had a chance to commit it. Is there any way of getting it back?red-scooter-62880
05/26/2022, 11:49 PMicy-controller-6092
05/27/2022, 4:23 AMthousands-jordan-32051
05/27/2022, 7:38 AMvar userTenantProvider = new Provider("UserTenantProvider", new ProviderArgs
{
TenantId = _config.Environment.ActiveDirectory.UserTenantId,
ClientId = _userTenantProviderConfig.ClientId,
ClientSecret = _userTenantProviderConfig.ClientSecret
});
The secret has been rotated and the new one is passed into the pipeline. However the pipeline still fails with the following message:
_building client: unable to obtain access token: clientCredentialsToken: received HTTP status 401 with response: {"error":"invalid_client","error_description":"AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '[secret]'._
The pipeline was working fine before the secret changed, it's as if the old one is cached somewhere. Any ideas?sparse-intern-71089
05/27/2022, 11:23 AMwhite-terabyte-21934
05/27/2022, 4:13 PMquick-airport-30353
05/27/2022, 4:44 PMelegant-zoo-39359
05/27/2022, 4:56 PMRetainOnDelete
to work with a Helm v3.Chart? If I delete a chart it continues to delete the associated k8s resources, instead of leaving them unchanged. Namespaces (for example) work as expected, so maybe it is something to do with Helm charts and/or the Go implementation? (Example code in the comments)curved-fish-7534
05/27/2022, 5:31 PMred-scooter-62880
05/27/2022, 7:37 PMlively-painting-61118
05/27/2022, 9:57 PMhelpful-motherboard-25571
05/28/2022, 2:18 AMsparse-rain-34573
05/29/2022, 8:52 AMconst alb = new awsx.elasticloadbalancingv2.ApplicationLoadBalancer ........
const appListenerHttps = alb.createListener.......
const zone = aws.route53.getZoneOutput({name:domainAddress})
const albDomain = new aws.route53.Record(`domain-record`, {
name: pulumi.interpolate `*.${domainAddress}`,
zoneId: zone.zoneId,
type: 'CNAME',
records: [appListenerHttps.endpoint.hostname]
});
export const albListenerArn = appListenerHttps.listener.arn
export const albArn = alb.loadBalancer.arn
*Application stack
const networkingStack = new StackReference(config.require('stack.networking'));
const alb = aws.applicationloadbalancing.getLoadBalancerOutput({arn:networkingStack.getOutput('albArn')});
const targetGroup = new awsx.elasticloadbalancingv2.ApplicationTargetGroup(
`app-alb-tg`,
{
...............
loadBalancer: new awsx.elasticloadbalancingv2.ApplicationLoadBalancer('alb',{
loadBalancer:alb <----error: Type 'GetLoadBalancerResult' is missing the following properties from type 'LoadBalancer': enableCrossZoneLoadBalancing, namePrefix, tagsAll, urn, getProvider
})
}
);
const itoolListener = new aws.lb.ListenerRule(
`app-alb-lstn`,
{
listenerArn: networkingStack.getOutput('albListenerArn'),
priority: 100,
actions: [
{
type: 'forward',
targetGroupArn: targetGroup.targetGroup.arn
}
],
conditions: [
{
hostHeader: {
values: [pulumi.interpolate`test.${domainAddress}`]
}
}
]
}
);
.....
acoustic-monitor-21868
05/30/2022, 9:40 AMpulumi up
on prod stack?average-cricket-80620
05/30/2022, 11:25 AMconst ecsCluster = new aws.ecs.Cluster(
'test',
{
name: 'test',
},
{
provider,
},
);
awslocal ecs describe-clusters --cluster test --region eu-central-1
shows this
{
"clusters": [
{
"clusterArn": "arn:aws:ecs:eu-central-1:000000000000:cluster/test",
"clusterName": "test",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0
}
],
"failures": []
}
But when I do pulumilocal down
I get this error
error: deleting urn:pulumi:localstack::Development::aws:ecs/cluster:Cluster::test: 1 error occurred:
* error waiting for ECS Cluster (arn:aws:ecs:eu-central-1:000000000000:cluster/test) to become Deleted: couldn't find resource (21 retries)
Even though it does exist. It does however get deleted properlythankful-coat-47937
05/30/2022, 7:29 PMDiagnostics:
pulumi:pulumi:Stack (toronto):
error: Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
* no matching EC2 VPC found
at Object.callback (/home/julian/betx/infra/node_modules/@pulumi/runtime/invoke.ts:162:33)
at Object.onReceiveStatus (/home/julian/betx/infra/node_modules/@grpc/grpc-js/src/client.ts:338:26)
at Object.onReceiveStatus (/home/julian/betx/infra/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
at Object.onReceiveStatus (/home/julian/betx//infra/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
at /home/julian/betx/infra/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
at processTicksAndRejections (node:internal/process/task_queues:78:11)
i am using a custom VPC for an ECS service, but trying to do pulumi up -v 4...7
doesn't seem to show anything useful. how can I debug this? for reference, i deleted the default VPC.icy-controller-6092
05/31/2022, 3:14 AMrich-agency-75207
05/31/2022, 4:20 AMgoogle native
provider and Google Cloud Key Management Service (KMS)
provider?
Pulumi uses: GOOGLE_CREDENTIALS
to support:
Pulumi in a non-interactive setting (for example CI/CD systems, where a person can not complete the normal gcloud auth application-default login flow).
which I have configured since Day 1. However, I recently changed secrets provider to Google's KMS service and I now must also define the GOOGLE_APPLICATION_CREDENTIALS
envvar with the same creds..?
Why the need for 2 x envvars?rich-agency-75207
05/31/2022, 4:21 AMadamant-father-26302
05/31/2022, 9:50 AMpulumi
CLI`late-nest-59850
05/31/2022, 11:00 AM