Skip to content
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

support alternate download endpoint urls #48

Merged
merged 5 commits into from
Mar 25, 2021
Merged

support alternate download endpoint urls #48

merged 5 commits into from
Mar 25, 2021

Conversation

dlethin
Copy link
Contributor

@dlethin dlethin commented Jan 19, 2018

This fix is meant to address #47

@ctaintor
Copy link
Contributor

It'd also be useful to provide the replacement regex. I have the same need as what you're saying, but my reverse proxy chops off more of the URL ( e.g. https://S3/bucket-name/asdf/* -> https://mysite.com/*)

@ctaintor
Copy link
Contributor

@dlethin - sent you a PR to support this

adds ability to control the regex for replacing s3 url with download_endpoint
@duro
Copy link

duro commented Apr 14, 2018

@ctaintor Any reason this was never merged. As I mentioned in #4 this would solve my problem of protecting my builds.

@duro
Copy link

duro commented Apr 14, 2018

For what it counts, I have pulled this fork into my project and it works flawlessly. Thanks!!

@JesseScott
Copy link

@dlethin merge conflicts - maybe sync with upstream and refresh the PR ? 🙏

@siddarthgandhi
Copy link
Contributor

PR synced with upstream.

@mikecsmith
Copy link

Any chance of this being merged? I would absolutely love this functionality due to my S3 bucket being hosted behind Cloudfront and not being publicly accessible.

@omerduzyol
Copy link
Contributor

I also need this feature as I've different public URLs for objects uploaded.

@hanno-jonlay
Copy link
Contributor

I also have a need for exactly this feature - Cloudfront seems to be the preferred way to share releases on S3 as it makes it a lot easier to add security features to control access to the assets. Our configuration means that the files are not actually accessible from the direct S3 URL at all.

I forked this branch and updated with the latest commits from the upstream master, to verify:
https://github.com/jonlay-hanno/fastlane-plugin-s3/tree/feature/optional-download-endpoint-update

Another confirmation on my end that the updated code works perfectly in my tests of a live app that we’re releasing.

@joshdholtz is there anything I can do to help get this merged? Happy to update the README with a better example, also, if that's blocking in any way.

@joshdholtz
Copy link
Member

I will take a look at this today! Just need to get a cup of ☕️ in my first 😊

@hanno-jonlay
Copy link
Contributor

Hey @joshdholtz - you are probably super busy with much more important things than this PR - just checking in to see whether there's any likelihood of this being merged.

I'll go down the hacky route if not, but would love to see this "natively" in fastlane_s3 if possible 😄

@joshdholtz
Copy link
Member

Let me get some coffee in me and then I’ll take a look at this PR!

Copy link
Member

@joshdholtz joshdholtz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great to me! Sorry for slow reply on this. No excuses but I have a my life sorted out now so I will be much faster going forward 😊

@joshdholtz joshdholtz merged commit 4cdd70d into fastlane-community:master Mar 25, 2021
@hanno-jonlay
Copy link
Contributor

🙌 Always appreciated. Thanks for all the time you put into this stuff.

a-tokyo added a commit to a-tokyo/fastlane-plugin-s3 that referenced this pull request Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants