Improve AP Gateway Build Command to Handle Same Name Local Policy Directories
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Current Limitation
Currently, local policies (filePath is given in manifest) are loaded to workspace's policies directory.
However, in a case where those directories has same name, that collision is not yet handled.
Even though this issue is not critical as users can give different names as a workaround and this is only applicable for local policies, its better to strict or handle such situations.
Suggested Improvement
Option A: Block from giving same name directories
Option B: Add the full path to workspace
Option C: Add a random hash to workspace folders
Option D: Handle only collision with appending a string
Version
No response
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 by tracing the AP Gateway build command and the loading of local policies whose manifest filePath is copied into the workspace policies directory. Decide which collision behavior is appropriate from the listed options, then verify that two same-name local policy directories are handled without overwriting each other.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100