Invalid or unknown key. Examine values at 'ServiceVcl.LoggingKineses'

[Ira-Varganovska]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

I'm getting error Invalid or unknown key. Examine values at 'ServiceVcl.LoggingKineses' when trying to add logging to Kineses.
The issue is reproduced on all versions 2.15.0, 3.X, 4.0.0.
The issue appears if loggingKineses is added to ServiceVclArgs (Servicev1Args)
Similar behavior is observed for loggingHerokus. All other types of logging args have no such issue.

Steps to reproduce

1. Create the service with argument loggingKineses: []
2. Run pulumi preview

Example

import * as fastly from "@pulumi/fastly";

const service = new fastly.ServiceVcl("my-service", {
  loggingKineses: [],
  backends: [{
       address: "127.0.0.1",
       name: "localhost",
       port: 80
   }],
  domains: [{
       comment: "demo",
       name: "demo.pulumi.com",
  }],
  forceDestroy: true,
});

Expected: No error is returned
Actual: has a problem: Invalid or unknown key. Examine values at 'ServiceVcl.LoggingKineses'.

[jkodroff]

@Ira-Varganovska Thanks for submitting this issue. It looks like name and topic are required attributes for loggingKinesis: https://www.pulumi.com/registry/packages/fastly/api-docs/servicevcl/#servicevclloggingkinese

Closing this issue, but please comment again if adding the required attributes does not resolve the issue for you.

[Ira-Varganovska]

Hi @jkodroff, thank you for your reply. As you could see from the example above, loggingKineses is an empty array, so no required fields should be impacting. Maybe my example was not a good one, this is also not working example:

           const service = new fastly.Servicev1("my-service", {
                loggingKineses: [{
                    name: 'kineses-logging',
                    topic: 'arn:aws:kinesis:us-east-1:####:stream/logs-cdn-test',
                    region: 'us-east-1',
                    iamRole: 'arn:aws:iam::####:role/cdn-kinesis'
                }],
                backends: [{
                    address: "127.0.0.1",
                    name: "localhost",
                    port: 80
                }],
                domains: [{
                    comment: "demo",
                    name: "demo.pulumi.com",
                }],
                forceDestroy: true,
            });
            

Error message:
fastly:index/servicev1:Servicev1 resource 'my-service' has a problem: Invalid or unknown key. Examine values at 'Servicev1.LoggingKineses'.

[rexoafastly]

Hi All. I am by no means a Pulumi expert but could this perhaps be a typo? The reference to Amazon Kinesis key in the example seems to be mis-spelled as loggingKineses, with an e instead of i. Thoughts?

[jkodroff]

@rexoafastly I would agree that it's a pluralization mistake (but the name actually is loggingKineses in the generated code). I think this weirdness is an issue with our pluralization where it thinks it's a Latin term, e.g. "thesis" -> "theses". Could you file a separate issue for the awkward spelling?

[Harry-027]

I'm also facing same issue ! Is it going to be resolved anytime soon ?