Modifying cli to be compatible with api. #9
Conversation
CAS-1945 CLI to match web functionality.
Bringing the CLI up to date with current functionality. The APIs have slightly changed because of projects. rick let's coordinate on this, I can take make sure the server-side is working. Functionality Must-have These already exist or need to be slightly updated because of new APIs
More to-do [ted]
Packaging
Marketing
More IdeasWhat are other onboarding things?
|
cased/cli.py
Outdated
| @@ -27,6 +27,8 @@ def cli(): | |||
| cli.add_command(logout) | |||
| cli.add_command(deployments) | |||
| cli.add_command(branches) | |||
| cli.add_command(projects) | |||
| cli.add_command(targets) | |||
|
|
|||
| # ... (keep the login and setup_target commands as they were) ... | |||
There was a problem hiding this comment.
| # ... (keep the login and setup_target commands as they were) ... |
There was a problem hiding this comment.
lol should ask this LLM to not generate those comments
| @@ -73,17 +74,17 @@ def build() -> None: | |||
|
|
|||
| project_name = get_repo_name() | |||
| secrets = extract_secrets_from_workflow(workflow_content) | |||
| create_secrets(project_name, secrets) | |||
| CasedAPI().create_secrets(project_name, secrets) | |||
There was a problem hiding this comment.
Thoughts about exporting the empty constructor form of this as just cased_api? cc @ivan-cased
There was a problem hiding this comment.
what do you mean?
There was a problem hiding this comment.
You could have cased_api = CasedAI() in another file, so is can be imported as cased_api. Not a big deal either way
There was a problem hiding this comment.
Oh yeah could be, may choose to do that in the branch_deploy PR, wanting to organize the error messages from api a bit and determine the final structure, right now we sys.exit on non 200 response, that's not a good way to implement or debug.
This changes
login,logout,projects,branches,targetsanddeploymentscased deployis split into another PR to make it more readable.Complete example:
