Feature suggestion: Allow user to set redirect options for the bucket
See original GitHub issueNow that the plugin allows for custom index and error documents ( #20 ), I think the next logical step on that path would be to allow users to specify the other two website configuration options: RedirectAllRequestsTo
and RoutingRules
(docs). Personally, I use routing/redirect rules on occasion, so it would be great to have the option to do this via the plugin (especially because these options get reset upon deploy currently).
I’d be happy to submit a PR for this if it’s something that you think you’d want to include.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
(Optional) Configuring a webpage redirect
Configure your bucket as a website by setting up redirect locations where you can redirect requests for an object to another object.
Read more >Allow option to redirect all requests to a s3 website bucket #23
I propose we add this parameter, thereby enabling this module to be used in creating s3 website buckets with the sole purpose of...
Read more >ConfigMap - NGINX Ingress Controller - Kubernetes
name type default
add‑headers string ""
allow‑backend‑server‑header bool "false"
allow‑snippet‑annotations bool true
Read more >Configure Grafana | Grafana documentation
Configuration file location. The default settings for a Grafana instance are stored in the $WORKING_DIR/conf/defaults.ini file. Do not change this file.
Read more >Redirect Users - Auth0
Because callback URLs can be manipulated by unauthorized parties, Auth0 recognizes only URLs on the AllowList set in the Allowed Callback URLs field...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You didn’t drop the ball at all–this was actually addressed in the refactor (#43) 😃. I’ll close this issue
This is related to one of the PRs I think I dropped the ball on. Assigning back to you to peek over after we merge/publish v2.