feat: integrate nexus API commands as first-class noun-verb subcommands#2019
Draft
feat: integrate nexus API commands as first-class noun-verb subcommands#2019
Conversation
f585042 to
c320e7a
Compare
b747ec2 to
6343984
Compare
Pull Request Test Coverage Report for Build 10fb78cd-b00c-4a9f-a1a6-a6ab27017b4dDetails
💛 - Coveralls |
b4ada07 to
24a3561
Compare
Auto-generate CLI commands from the Astronomer API spec via nexus and register them directly on the root in noun-verb format (e.g. `astro deployment create`). Nexus commands take priority; remaining cloud commands fill gaps via automatic merge. This removes ~70 hand-written cloud commands now covered by the API spec. Key changes: - Add ConfigAdapter bridging astro-cli's viper config to nexus - Register nexus commands in noun-verb format on root command - Merge cloud commands underneath nexus nouns (nexus-first priority) - Preserve `astro deploy` action semantics alongside nexus deploy noun - Remove superseded deployment/workspace/organization cloud commands (CRUD, user/team/token management, inspect, hibernate, wake-up) - Add interactive prompts for required body fields (with retry loops) - Add delete confirmation prompts with --force bypass - Pretty-print JSON output in terminals; raw JSON when piped - Format API errors as "Error (<status>): <message>" - Add BREAKING_CHANGES.md documenting all removals and changes
db46713 to
42d4bbd
Compare
astro nexus subcommands
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Auto-generate CLI commands from the Astronomer API spec via the nexus shared library and register them directly on the root in noun-verb format (e.g.
astro deployment create). Nexus commands take priority; remaining cloud commands fill gaps via automatic merge. This removes ~70 hand-written cloud commands now covered by the API spec.Key changes
ConfigProviderinterface, mapping domains to API profiles and contexts to org/workspace/deployment defaultscreate-deployment) are parsed and registered asastro <noun> <verb>(e.g.astro deployment create)astro deploy,astro deployment connection,astro deployment airflow-variable)deletecommands prompt for confirmation;--force/-fskips the promptError (<status>): <message>instead of raw JSONBREAKING_CHANGES.mddocuments all removed commands, removed features, and behavioral changes🧪 Functional Testing
astro deployment list— should return pretty-printed JSON in terminalastro deployment create— should prompt for required fields (type, name, etc.)astro deployment delete <id>— should prompt for confirmation;--forceskips itastro deployment list | jq '.'— should return raw compact JSON when pipedastro deploy— should still work as before (project deployment)astro workspace list/astro organization list— nexus-generated commands workastro deployment connection list)📋 Checklist
make testbefore taking out of draftmake lintbefore taking out of draft