Skip to content

docs: Interactive domain purchase design - #188

Merged
jpage-godaddy merged 3 commits into
mainfrom
interactive-domain-purchase-design
Aug 7, 2026
Merged

docs: Interactive domain purchase design#188
jpage-godaddy merged 3 commits into
mainfrom
interactive-domain-purchase-design

Conversation

@rts1-godaddy

Copy link
Copy Markdown
Collaborator

Proposal to support an Interactive domain purchase for cli users. This is intended for humans use only.

Copilot AI lite review requested due to automatic review settings August 6, 2026 19:33
### Command Signature

```
gddy domain register [DOMAIN] [--interactive | --non-interactive]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should have multiple entry points here. Users may start instead with gddy domain suggest --interactive and be presented with a search interface that then leads through the purchase flow.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, updated the design to support this. Any domain subcommand can hand off to the purchase wizard via --interactive:

  • gddy domain suggest "cool startup" --interactive → pick from suggestions → continue to purchase
  • gddy domain available example.com --interactive → if available, continue to options/purchase
  • gddy domain quote example.com --interactive → jump straight to review & confirm

The command does its normal work first, then instead of exiting, it feeds the result into the wizard and continues from the appropriate step. Same state machine, different starting points.

Commands that don't naturally lead to a purchase (domain list, domain get, domain contacts init) ignore the flag.

}
```

This preserves scriptability: `gddy domain register 2>/dev/null` gives clean JSON even when the interactive wizard ran.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I prefer the human output mode for interactive flows. Preserving scriptability seems moot to me if you're doing an interactive experience.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. I will update the design to

  • Interactive mode → human output by default (summary, colors, next-steps guidance on stdout)
  • Non-interactive mode (--non-interactive or no TTY) → JSON envelope as usual for scripting/agent consumption
  • User can still force JSON with --output json if they want structured output after an interactive session (edge case, but supported)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@jpage-godaddy jpage-godaddy changed the title Interactive domain purchase design docs: Interactive domain purchase design Aug 7, 2026
@jpage-godaddy
jpage-godaddy merged commit e83d429 into main Aug 7, 2026
4 of 5 checks passed
@jpage-godaddy
jpage-godaddy deleted the interactive-domain-purchase-design branch August 7, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants