-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring S3 Bucket to v1beta1 #331
Conversation
Minor update, support for the following has been added:
The following operations will need to be separated out into other resources, similar to the S3 Bucket Policy:
|
6a3043d
to
fb12523
Compare
@krishchow Do you plan on including those resources in this PR? I think deferring them to another PR would be better. |
@muvaf - That was my plan as well, I think they can be created a later date - as for this PR, the core logic for the controller/client should be finished now. I am just working on adding some testing for the new s3 bucket. |
3bfd8df
to
f2e62b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great start! I have left some high level comments and went into a bit more detail for LifecycleConfiguration
functionality, which could apply to other substructs. I believe, in general, we strive for the least amount of indirections and functions so that it's simpler to understand. That comes with some cost due to duplication or unaesthetic but the simplicity is usually worth it.
ad36109
to
1ddad67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's coming together! I've left some comments around simplifications but I believe the approach is solid and makes it easier to deal with that archaic API.
545a389
to
4cffead
Compare
@muvaf - any chance you can review this prior to Thursday? I believe pretty much everything should be done at this point aside from some minor cleanup work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good to me. I have left some minor comments and I'd prefer not to use in.config
at all in the resource controllers if possible since *v1beta1.Bucket
is already available.
Let me know when this is ready to merge. I can follow up with a small PR for those comments.
a5e43ab
to
87b05d5
Compare
e226398
to
f4f2648
Compare
… Bucket controller Signed-off-by: Muvaffak Onus <onus.muvaffak@gmail.com> Signed-off-by: Krish Chowdhary <krish@redhat.com>
…or creation, deletion and validation Signed-off-by: Krish Chowdhary <krish@redhat.com>
Signed-off-by: Krish Chowdhary <krish@redhat.com>
… expanded testing code for bucketcontrollers Signed-off-by: Krish Chowdhary <krish@redhat.com>
… as requested in PR Signed-off-by: Krish Chowdhary <krish@redhat.com>
…unctions, moved to under pkg/controller Signed-off-by: Krish Chowdhary <krish@redhat.com>
…rk on subcontroller testing Signed-off-by: Krish Chowdhary <krish@redhat.com>
Signed-off-by: Krish Chowdhary <krish@redhat.com>
…oller testing, added all tests for the bucket resource Signed-off-by: Krish Chowdhary <krish@redhat.com>
… bucket examples Signed-off-by: Krish Chowdhary <krish@redhat.com>
f4f2648
to
4d76f77
Compare
Signed-off-by: Krish Chowdhary <krish@redhat.com>
4d76f77
to
b935c3e
Compare
Thank you @krishchow !! This is one of the oldest AWS API and we finally covered it with the managed reconciler! |
…ctor Bring S3 Bucket to v1beta1
…ctor Bring S3 Bucket to v1beta1
Moving schemas (3) resources to v1beta1 version
Description of your changes
Fixes #99 #331
This PR aims to bring the S3 Bucket to v1beta1 by adding support for related resources and API calls for AWS S3.
Currently, there is support for the following API calls:
There are plans to implement support for:
Bucket Policy has already been implemented in a prior PR :)
Checklist
I have:
make reviewable
to ensure this PR is ready for review.app.yaml
to include any new role permissions.