redhat-developer / redhat-developer/mapt
[enhancement] Azure location managed using ENVs instead of flag
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
This is interesting as I did not take those ENVs into consideration (this is the reason why there is a location param) for azure provider which actually kind of break this idea with the DefaultHostingPlace 🤔 may worthwhile to create a issue as following one for this one to use ENVs instead of location.
Originally posted by @adrianriobo in https://github.com/redhat-developer/mapt/issues/621#issuecomment-3375346967
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 Azure provider's location parameter and how the DefaultHostingPlace behavior relates to Azure environment variables. Compare this issue with the referenced issue 621 and define the expected precedence and completion criteria before changing the provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100