feat: Add ddev spec for DDEV

[khalwat]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Spec addition: ddev for the DDEV local development environment

What is the current behavior? (You can also link to an open issue here)

Currently ddev is not available

What is the new behavior (if this is a feature change)?

Adds the ddev spec

Additional info:

Leverages the Fig-provided Cobra module for generating the spec directly from the ddev command: https://github.com/drud/ddev/pull/4216

[withfig-bot]

Overview

src/ddev.ts:

Info:

[withfig-bot]

Hello @khalwat, thank you very much for creating a Pull Request! Here is a small checklist to get this PR merged as quickly as possible:

• [ ] Do all subcommands / options which take arguments include the args property (args: {})?
• [ ] Are all options modular? E.g. -a -u -x instead of -aux
• [ ] Have all other checks passed?

Please add a 👍 as a reaction to this comment to show that you read this.

[clo4]

Looks good! Can you run npm run lint:fix to fix the linting errors?

[khalwat]

Done. FWIW, the output here is coming directly from your own Cobra tool:

https://fig.io/docs/guides/integrating/integrations/cobra

...so if what it outputs isn't passing linting, probably it should be fixed as well?

[clo4]

Agreed! It's not a huge deal because the linting errors can be fixed automatically and will be fixed when using our push to autocomplete CI action, but agreed, it should be as close as possible to the intended output by default.

[clo4]

cc @fedeci

[khalwat]

If there's anything else you need me to do here, just let me know.

[khalwat]

How does it work in terms of an actual release that will be available for people to use?

[fedeci]

@khalwat specs are automatically published once they are merged in but, because of caches (npm registry and our CDN provider), they often need a couple days before being publicly available.