SalesforceCommerceCloud / SalesforceCommerceCloud/b2c-developer-tooling

Implement ecdn firewall commands (list/create/get/update/delete/reorder)

Open
#299 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
53
Forks
19
Avg merge
1d 4h
Merged PRs (30d)
33

Description

Summary

The eCDN firewall commands were documented but never implemented. These commands would manage custom firewall rules on CDN zones.

Commands to Implement

  • b2c ecdn firewall list — List custom firewall rules
  • b2c ecdn firewall create — Create a custom firewall rule
  • b2c ecdn firewall get — Get a firewall rule
  • b2c ecdn firewall update — Update a firewall rule
  • b2c ecdn firewall delete — Delete a firewall rule
  • b2c ecdn firewall reorder — Reorder firewall rules

Context

Discovered during v1.0 GA readiness audit. Documentation and oclif topic entries were removed in the cleanup PR. The oclif topic in package.json and docs in docs/cli/ecdn.md were referencing non-existent commands.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with package.json and docs/cli/ecdn.md to understand the removed eCDN firewall topic and documented command surface. Trace the existing eCDN CLI entry points and API patterns before implementing list, create, get, update, delete, and reorder; done means all six commands are available and manage custom firewall rules on CDN zones.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.