magnificent-sugar-64951
05/21/2023, 9:39 AMmagnificent-sugar-64951
05/21/2023, 9:39 AMrefined-rose-1179
05/21/2023, 7:15 PMError creating ForwardingRule: googleapi: Error 400: Invalid value for field 'resource.target':
Invalid target type TARGET_HTTP_PROXY for forwarding rule in scope REGION, invalid
`const proxy = new gcp.compute.TargetHttpProxy('backend-api-proxy', {
urlMap: urlMap.selfLink,
name: 'backend-api-proxy',
});
// // Create a forwarding rule
const forwardingRule = new gcp.compute.ForwardingRule(
'backend-api-http-forwarding-rule',
{
name: 'backend-api-http-forwarding-rule',
region: 'europe-west1',
target: proxy.selfLink,
ipAddress: '0.0.0.0',
portRange: '80',
}
);
better-activity-84090
05/22/2023, 1:27 PMname : "my-stack-audit-d21bbd9" => "my-stack-audit-6494e4d"
I could not find any configuration explaining why that would happen, and downgrading back to an older version doesn’t seem to work
Anybody had the same issue ? Or have an idea on how to debug it ?
Thanksquaint-river-59320
05/22/2023, 2:41 PMambitious-father-68746
05/22/2023, 3:45 PMerror: update is marked constrained, but is not constrained to an update or a replace
I've never seen this before and I've been using Pulumi for a long time. What does this actually mean? Thanksambitious-father-68746
05/22/2023, 4:02 PMambitious-father-68746
05/22/2023, 4:18 PM--target
and --replace
together. If I only use --replace
I don't get the error, but it's only targeting those resources, not everything else in the stack. I think this is not correct.elegant-laptop-80400
05/22/2023, 6:57 PMstraight-cat-87033
05/23/2023, 12:14 AMimport
resource option:
The docs state that:
The resulting Pulumi program, after the import is complete, will faithfully generate the same desired state as your existing infrastructure’s actual state.
Because of this, all properties need to be fully specified. If you forget to specify a property, or that property’s value is incorrect, you’ll first receive a warning during preview, and then an error during the actual import update.But that isn’t matching the behavior that I’m seeing with regards to unspecified properties.
ambitious-father-68746
05/23/2023, 7:25 AMmodern-musician-3045
05/23/2023, 7:34 AMpulumi version
also pulumi will tell you when it runs if it is not the latest version and suggest you update… well it does on the mac version anywayenough-honey-14480
05/23/2023, 9:45 AMenough-honey-14480
05/23/2023, 9:46 AMadorable-advantage-6937
05/23/2023, 2:28 PMconst cluster = new aws.ecs.Cluster(envRelated('st-primary-ecs-cluster'));
const alb = new <http://awsx.lb|awsx.lb>.ApplicationLoadBalancer(
envRelated("stp-loadbalancer"), {subnetIds: vpc.publicSubnetIds,listeners: [{
port: 443,
protocol: "HTTPS",
certificateArn: certificateArn,
defaultActions: [{ type: "forward", targetGroupArn: ??? },],
} ,
{
port: 80,
protocol: "HTTP",
defaultActions: [
{
type: "redirect",
redirect: {
port: "443",
protocol: "HTTPS",
statusCode: "HTTP_301",
},
},
],
}]});
const repo = new awsx.ecr.Repository(envRelated("ecr-st-repo"), {
forceDelete: true,
});
const imgApi = new awsx.ecr.Image(envRelated('st-api'), { repositoryUrl: repo.url, path: "./api", target: 'production' });
const appServiceApi = new awsx.ecs.FargateService("st-api-svc", {
cluster: cluster.arn,
assignPublicIp: true,
taskDefinitionArgs: {
container: {
image: imgApi.imageUri,
cpu: 102 /*10% of 1024*/,
memory: 50 /*MB*/,
essential: true,
portMappings: [ {containerPort: containerPort , targetGroup: alb.defaultTargetGroup} ],
},
},
desiredCount: 1,
});
purple-train-14007
05/23/2023, 3:49 PMpurple-train-14007
05/23/2023, 3:54 PMpurple-train-14007
05/23/2023, 3:55 PMerror: read ".pulumi\\meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): AccessDenied: Access Denied
status code: 403, request id: CFMV7QGJSA2MJP27, host id: p2YUjMFtIJW5Npm50JU7A7IaTsJ2m8xznrnZf8lPrRno8H2WkOA6zpO8ZGeMpHz84/+z/svnWJ0=
clever-dog-35937
05/23/2023, 7:03 PMpulumi-aws-iam
for about three weeks now, is there some standard to notify for review that I'm missing?
https://github.com/pulumi/pulumi-aws-iam/pull/12damp-lock-9822
05/23/2023, 8:03 PMUnhandled exception: Error: Invoke: Default provider for 'aws' disabled. 'aws:ec2/getAmi:getAmi' must use an explicit provider
.adorable-analyst-27426
05/23/2023, 11:59 PMerror: .pulumi/stacks/nonprod.json: snapshot integrity failure; refusing to use it: resource urn:pulumi:nonprod::ai::azure:appservice:HttpEventSubscription$azure:appservice/functionApp:FunctionApp::api dependency refers to missing resource
from AzureDevOps job using branch, it was runing OK until today. Nothing has change from and just want to add dummy data to the API, any advicebrief-car-60542
05/24/2023, 12:08 AM{
dependsOn: [
restApiPolicys[region]
],
provider: config.providers[configEnvironment] as aws.Provider,
},
aloof-leather-66267
05/24/2023, 2:19 AMname
changed, but in reality, nothing has changed. Why is this, and how can I fix it?hallowed-camera-71190
05/24/2023, 4:40 AMfancy-pharmacist-39201
05/24/2023, 7:01 AMpulumi up
because Pulumi incorrectly thinks it needs to recreate all my resources. I tried pulumi stack export
but I don't know with what to replace the token
and apiToken
input and output strings in the providers: when I replace them with the appropriate encrypted values from my Pulumi.<stack>.yaml
file, I get "could not deserialize deployment: invalid character 'Y' after top-level value" on the import, so presumably they need to be somehow different between the state file and the stack config file. I also tried pulumi refresh --target <urn of the provider>
, but that appears to have been a no-op; and pulumi up --target <urn of the provider>
said there was no resource with that URN. How can I tell Pulumi to use the correct credentials in a refresh operation?tall-computer-65747
05/24/2023, 9:26 AMpulumi refresh
I'm seeing a lot of timeout errors around Kafka ACLs and service accounts. This wasn't an issue before but seems to correlate with onboarding more Kafka service accounts. If I retry the refresh multiple times it eventually persists, but this isn't ideal. I was wondering if anyone has encountered this before? Or if it is pulumi getting rate limited by the Confluent API? Thanks 🙂gorgeous-monkey-78209
05/24/2023, 10:10 AMv2023-02-01
of the Azure API, which was available in the v1.99.0 Pulumi provider but we're running in to problems with Pulumi refusing to acknowledge the new AKS SKU name change that's mandatory from that version onwards. We thought we'd try a newer provider version and see if it had a newer API too but the latest API version available in v1.99.1 and up has dropped back to v2023-01-01
.
Would it be advisable to open an issue on GitHub or has anyone got any advice on if they've encountered similar issues with versioning? Thanks muchly!adorable-analyst-27426
05/24/2023, 11:50 AMred-airline-54646
05/24/2023, 12:29 PMerror: obtain subscription(***) from Azure CLI: parsing json result from the Azure CLI: waiting for the Azure CLI: exit status 1: ERROR: Please run 'az login' to setup account.
any thoughts what's missing?
- bash: |
echo "Pulumi: $(pulumi version)"
pulumi login <azblob://platform>
pulumi stack select ${{ parameters.stack }}-${{ parameters.environment }}
displayName: Login to Pulumi
- bash: |
# Configure azure-native provider.
pulumi config set azure-native:tenantId $(tenant-id)
pulumi config set azure-native:subscriptionId $(subscription-id)
pulumi config set azure-native:clientId $(app-id)
pulumi config set azure-native:clientSecret $(app-secret) --secret
# Configure azuread provider.
pulumi config set azuread:tenantId $(tenant-id)
pulumi config set azuread:clientId $(app-id)
pulumi config set azuread:clientSecret $(app-secret) --secret
displayName: Configure Pulumi providers
cool-dress-96114
05/24/2023, 4:36 PMNote
In May 2022, AWS KMS changed the rotation schedule for AWS managed keys from every three years (approximately 1,095 days) to every year (approximately 365 days).
New AWS managed keys are automatically rotated one year after they are created, and approximately every year thereafter.
Existing AWS managed keys are automatically rotated one year after their most recent rotation, and every year thereafter.
Will this break our stacks / all of our secret configuration?