redhat-developer / redhat-developer/mapt
[spike] Evaluate the structure to make usage of multi provider dns domain management
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
A cool feature to be added is add domain names to the targets created by mapt, the pattern can be applied i.e.
The outcome for the spike si to evaluate what is needed and create a set of issues around the work on each supported provider / component
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 reviewing mapt's supported providers and components, then read the linked multi-provider DNS delegation example. Define what is needed to add domain names to targets created by mapt and split the provider/component work into follow-up issues. Done means the spike findings and actionable issue set are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, gcp
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100