-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: enable reusable credentials for S3 integration #248
feat: enable reusable credentials for S3 integration #248
Conversation
2a16e90
to
08140ca
Compare
08140ca
to
4b0a7d1
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #248 +/- ##
==========================================
+ Coverage 63.82% 65.12% +1.30%
==========================================
Files 26 28 +2
Lines 633 671 +38
Branches 30 32 +2
==========================================
+ Hits 404 437 +33
+ Misses 222 220 -2
- Partials 7 14 +7 ☔ View full report in Codecov by Sentry. |
a53dec0
to
03612d4
Compare
- Introduces the "objectName" property to store the S3 object name - Refactors "keyName" to exclusively handle secret aliases - Renames "keyPrefix" to "objectPrefix" - Utilizes Part list size for naming of destination objects
03612d4
to
bbb2b1c
Compare
This pull request is stale because it has been open for 7 days with no activity. |
…into feat/reusable_credentials_new_proposal # Conflicts: # DEPENDENCIES
61d8d5b
to
7910ff0
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.
@yurimssilva generally lgtm. I would be a bit more specific on the examples, providing an example for the use of keys via the vault and the use of the not-recommended clear-text credentials. Probably both examples right below the respective method of using the credentials.
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.
Thanks, @gerbigf . New examples have been added to the documentation.
...va/org/eclipse/edc/connector/provision/aws/s3/S3ConsumerResourceDefinitionGeneratorTest.java
Outdated
Show resolved
Hide resolved
...ane-aws-s3/src/main/java/org/eclipse/edc/connector/dataplane/aws/s3/S3DataSourceFactory.java
Outdated
Show resolved
Hide resolved
extensions/common/aws/aws-s3-core/src/main/java/org/eclipse/edc/aws/s3/S3BucketSchema.java
Show resolved
Hide resolved
extensions/common/aws/aws-s3-core/src/main/java/org/eclipse/edc/aws/s3/S3BucketSchema.java
Show resolved
Hide resolved
extensions/common/aws/aws-s3-core/src/main/java/org/eclipse/edc/aws/s3/S3BucketSchema.java
Outdated
Show resolved
Hide resolved
5ad02aa
to
8619651
Compare
…into feat/reusable_credentials_new_proposal # Conflicts: # extensions/control-plane/provision/provision-aws-s3/src/test/java/org/eclipse/edc/connector/provision/aws/s3/S3ConsumerResourceDefinitionGeneratorTest.java
8619651
to
7de30dd
Compare
} | ||
}); | ||
|
||
if (Stream.of(OBJECT_NAME, KEY_NAME, OBJECT_PREFIX, KEY_PREFIX) |
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.
given that KEY_NAME and KEY_PREFIX have been deprecated, I would avoid checking them, given that this validator is triggered on asset create/update
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.
The idea was to include them to be compatible with assets already stored in previous versions, as the validation is also run at DataSource
creation, and then remove them after the deprecation period.
What this PR changes/adds
objectName
property to store the S3 object namekeyName
to exclusively handle secret aliaseskeyPrefix
toobjectPrefix
Part
list size.Why it does that
To align with the existing behavior of
TransferProcessManagerImpl
, which defaults to usingkeyName
for fetching secret values, rather than introducing a new property configuration specifically for holding the secret alias, a more effective approach would be to introduce anobjectName
property to store the S3 object name. This modification aims to enhance consistency and also alignment between theAWS
andAzure
platforms.Linked Issue(s)
Closes #211