aws-amplify / aws-amplify/amplify-hosting
can't unckeck access restriction
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
d3fwj1dkns35sh
### AWS Region
us-west-2
### Amplify Hosting feature
Access control
### Describe the bug
After enabling access restriction for auto-detected branches it can not be disabled.
### Expected behavior
I expect to be able to disable access restriction (which I enabled myself) for auto-detected branches.
Or I would expect if anything is going wrong I get the proper error message when I save the settings.
### Reproduction steps
1. Go to App settings > Edit
2. Enable branch auto-detection
3. Enable "Restrict access to autodetected branches with a username and password."
4. Click Save
5. Go to App settings > Edit
6. Disable "Restrict access to autodetected branches with a username and password."
7. Click Save
8. Refresh the Page and go to App settings > Edit
9. The "Restrict access to autodetected branches with a username and password." is still enabled.
### Build Settings
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
Contributor guide
Research direction
Start by reproducing the issue in Amplify Hosting for app d3fwj1dkns35sh in us-west-2, following the App settings > Edit steps in the report. Check the saved access-control state after disabling restriction for auto-detected branches. Done means the setting remains disabled after saving and refreshing, or a proper error is shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100