SSWConsulting / SSWConsulting/SSW.Website
🧑💻 DevOps - Add Better CORS Settings
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
As per my conversation with @wicksipedia, our CORS rules may need specified allowedOrigins in the archiveStorage.bicep file.
### Tasks
- [ ] Investigate adding specified URLs in CORS settings
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with archiveStorage.bicep and inspect its current CORS configuration and allowedOrigins handling. Determine which specified URLs the deployment requires, then update the file so the intended origins are explicitly represented. Done means the tasklist investigation is resolved with the required CORS origins configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100