Support slice fields in S3 buckets #914
Assignees
Labels
kind/enhancement
Categorizes issue or PR as related to existing feature enhancements.
Comments
RedbackThomson
added
kind/enhancement
Closed
ack-bot
pushed a commit
to aws-controllers-k8s/s3-controller
that referenced
this issue
Oct 27, 2021
Implements aws-controllers-k8s/community#914 Description of changes: Uses the new custom fields code-generator PR (aws-controllers-k8s/code-generator#222) to create lists of configuration types. At runtime each of these configurations is put individually (mapped using their ID field) onto the bucket. For each reconciliation, we describe the configurations using a `List*` operation and determine the delta for each configuration using a generated `compare*` method in the `sdk.go`. The configuration elements are individually created, deleted, updated or no-op'd depending on the diff. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Requires implementation of #881
The following properties of S3 buckets slices of structs to be supported in the spec:
AnalyticsConfigurationIntelligentTieringConfigurationInventoryConfigurationMetricsConfigurationDescribe the solution you'd like
The S3 API supports adding any number of those configuration objects, associated with an ID used for fetching it later. Each of these properties will require a slice of custom structs. Each of these structs should have an identifier and a configuration object. There is no such type in any of the
Put*fields, because anyPut*field deals with only a single instance of the configuration, whereas the spec will deal with the collection of desired instances.The text was updated successfully, but these errors were encountered: