Closed giedri closed 3 months ago
Updates Upbound AWS provider to the latest version (1.2.1) Adds optional flag to switch off composition schema aware validation feature to supress warnings if necessary.
I've tested this configuration by deploying sqs-lambda-s3 and microservice examples, both were deployed without any errors.
I see warnings can be suppressed and there are no errors. @giedri are there any warnings for the two compositions you tested?
Warnings while deploying serverless samples: sqs-lambda-s3 git:(main) kubectl apply -k . <...> Warning: Composition "container.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[0].patches[0].patchSets[0].patches[1].toFieldPath: Invalid value: "spec.forProvider.region": field 'region' is not valid according to the schema Warning: Composition "container.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[1].patches[0].patchSets[0].patches[1].toFieldPath: Invalid value: "spec.forProvider.region": field 'region' is not valid according to the schema Warning: Composition "container.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[2].patches[0].patchSets[0].patches[2].fromFieldPath: Invalid value: "spec.resourceConfig.tags": field 'tags' is not valid according to the schema Warning: Composition "container.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[2].patches[2].toFieldPath: Invalid value: "spec.forProvider.functionName": field 'functionName' is not valid according to the schema composition.apiextensions.crossplane.io/container.lambda.aws.upbound.awsblueprints.io created <...> Warning: Composition "s3.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[0].patches[0].patchSets[0].patches[1].toFieldPath: Invalid value: "spec.forProvider.region": field 'region' is not valid according to the schema Warning: Composition "s3.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[1].patches[0].patchSets[0].patches[1].toFieldPath: Invalid value: "spec.forProvider.region": field 'region' is not valid according to the schema Warning: Composition "s3.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[2].patches[0].patchSets[0].patches[2].fromFieldPath: Invalid value: "spec.resourceConfig.tags": field 'tags' is not valid according to the schema Warning: Composition "s3.lambda.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[2].patches[2].toFieldPath: Invalid value: "spec.forProvider.functionName": field 'functionName' is not valid according to the schema composition.apiextensions.crossplane.io/s3.lambda.aws.upbound.awsblueprints.io created <...> Warning: Composition "sqs.esm.awsblueprints.io" invalid for schema-aware validation: spec.resources[0].patches[0].patchSets[0].patches[3].toFieldPath: Invalid value: "spec.forProvider.tags": field 'tags' is not valid according to the schema composition.apiextensions.crossplane.io/sqs.esm.awsblueprints.io created Warning: Composition "sqs.queue.aws.upbound.awsblueprints.io" invalid for schema-aware validation: spec.resources[0].patches[0].patchSets[0].patches[3].fromFieldPath: Invalid value: "spec.resourceConfig.tags": field 'tags' is not valid according to the schema composition.apiextensions.crossplane.io/sqs.queue.aws.upbound.awsblueprints.io created <...> Warning: CustomResourceDefinition.apiextensions.k8s.io "XFanout.awsblueprints.io" not found Warning: CustomResourceDefinition.apiextensions.k8s.io "XEncryptionKey.awsblueprints.io" not found composition.apiextensions.crossplane.io/xsnssqslambdas3.awsblueprints.io created
What does this PR do?
Updates Upbound AWS provider to the latest version (1.2.1) Adds optional flag to switch off composition schema aware validation feature to supress warnings if necessary.
Motivation
More
[X] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
I've tested this configuration by deploying sqs-lambda-s3 and microservice examples, both were deployed without any errors.
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)
Note:
For Moderators
Additional Notes