s3 loggingConfiguration missing targetObjectKeyFormat support

[saatvik-chugh]

What happened?

The s3.aws.crossplane.io/v1beta1 Bucket resource supports spec.forProvider.loggingConfiguration, but there does not appear to be a field to set the S3 server access log object key format (TargetObjectKeyFormat).

AWS supports TargetObjectKeyFormat for bucket logging, allowing either SimplePrefix or PartitionedPrefix. Terraform/OpenTofu and the Upbound AWS S3 provider expose this as targetObjectKeyFormat.

This prevents configuring the newer partitioned S3 server access log key format from provider-aws.

How can we reproduce it?

Try to configure an S3 bucket logging configuration with a partitioned prefix/object key format.

Expected shape, conceptually:

apiVersion: s3.aws.crossplane.io/v1beta1
kind: Bucket
spec:
  forProvider:
    locationConstraint: us-east-1
    loggingConfiguration:
      targetBucket: my-log-bucket
      targetPrefix: logs/
      targetObjectKeyFormat:
        partitionedPrefix:
          partitionDateSource: EventTime

There is no targetObjectKeyFormat field in the LoggingConfiguration schema.

What environment did it happen in?

Provider version: v0.56.0 / v0.58.0
Kubernetes version:
Crossplane version:
AWS region:

Related references

AWS S3 PutBucketLogging supports TargetObjectKeyFormat.
Upbound provider-aws-s3 BucketLogging exposes targetObjectKeyFormat.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.