cloudposse / cloudposse/terraform-cloudflare-zone

Break up module into smaller modules

Open
#40 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HCL
Stars
35
Forks
28
PR merge metrics
No merged PRs in 30d

Description

### Describe the Feature

Cloudflare is a lot like AWS. It's turning into its own cloud.

They have r2, workers, dns, waf, rate limit rules, pages, transform rules, etc. Most of these resources are either attributed to the account or to a domain (zone in cloudflare lingo). Thus, thus module dedicated to a zone would encourage a teralith.

### Expected Behavior

Break apart the existing module into separate modules

### Use Case

Fewer resources managed by a single module

### Describe Ideal Solution

See above

### Alternatives Considered

_No response_

### Additional Context

- current resources managed https://github.com/cloudposse/terraform-cloudflare-zone?tab=readme-ov-file#resources
- New ones on the way https://github.com/cloudposse/terraform-cloudflare-zone/issues

Contributor guide

Open the contributing guide

Research direction

Start with the current resources listed in the module README and review the linked issue for planned additions. Group resources by account or zone ownership and determine the module boundaries before changing files. Done means the existing monolithic module is split into smaller modules that manage fewer resources each.

Written by the indexing model from the issue text.

Assessment

Tech stack
terraform
Domain
cloud, infrastructure
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.