-
Notifications
You must be signed in to change notification settings - Fork 369
Ability to get s3:// URI back from an S3 resource #361
Comments
I want to help. Where should I look into.? |
@tmnuwan12 go for it. Just keep in mind that whatever we do here should stay backward compatible. |
Can you assign it to me.. But I need some time with this if that's ok. I have some office stuff to clear out this week. |
For bug fixes do we need to branch off from master or 2.2.x branch..? |
Good question! Ideally from 2.2.x |
I checked the code for SimpleStorageResource. From what I understand from the requirement is ability to specify "s3://" endpoint when creating SimpleStorageResource and return |
I think it it should be possible to obtain s3:// and https:// no matter how what parameters were passed to the constructor. What do you think? |
agreed @maciejwalkowiak |
@osi @maciejwalkowiak Yes I agree. What do you think about adding getURI() implementation for SimpleStorageResource class that provides the "s3://" URI. |
@maciejwalkowiak I am getting some compilation errors when running maven tests ( but in Intellij editor no compilation errors). Is this something known issue or am I missing something..? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project spring-cloud-aws-core: Compilation failure: Compilation failure: Also I am getting a warning in the build logs as below not sure anything related. [WARNING] Could not transfer metadata org.springframework.boot:spring-boot-dependencies:2.4.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots (https://repository.apache.org/snapshots): peer not authenticated |
@tmnuwan12 I explained reasons for compilation failure here #565 (review). Lets continue discussion in the pull request. |
I am trying to "round-trip" resources from a s3:// URI into a
Resource
and back again. Currently,SimpleStorageResource#getURL
returns ahttps://
URI into AWS.It would be nice to be able to round-trip these URIs
The text was updated successfully, but these errors were encountered: