Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(cli): docs, doctor, context commands do not use configuration directly anymore #32578

Merged
merged 10 commits into from
Dec 20, 2024

Conversation

kaizencc
Copy link
Contributor

@kaizencc kaizencc commented Dec 18, 2024

This is a refactor that follows #32558. The effort is to ensure that the configuration object is not directly used by commands and instead, the relevant information is passed directly to the function.

  • doctor: no options needed
  • docs: 1 option needed
  • context: in addition to a few options, the context command also saves some values to cdk.context.json. this requires some modifications to the Context object to support this.

We move away from using the archaic API in command-api.ts. This seems to be an old effort to standardize CLI commands that was only used for doctor/docs/context. We have since evolved to use command-specific property bags.

Since this is a refactor PR. I aim to change no functionality of the CLI.

Checklist


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@kaizencc kaizencc requested a review from a team as a code owner December 18, 2024 18:40
@github-actions github-actions bot added the p2 label Dec 18, 2024
@aws-cdk-automation aws-cdk-automation requested a review from a team December 18, 2024 18:41
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Dec 18, 2024
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

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

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

@aws-cdk-automation aws-cdk-automation added the pr/needs-cli-test-run This PR needs CLI tests run against it. label Dec 18, 2024
Copy link

codecov bot commented Dec 18, 2024

Codecov Report

Attention: Patch coverage is 96.15385% with 1 line in your changes missing coverage. Please review.

Project coverage is 80.41%. Comparing base (3377c3b) to head (699fe73).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #32578      +/-   ##
==========================================
+ Coverage   79.15%   80.41%   +1.26%     
==========================================
  Files         107      106       -1     
  Lines        7139     6955     -184     
  Branches     1321     1288      -33     
==========================================
- Hits         5651     5593      -58     
+ Misses       1304     1183     -121     
+ Partials      184      179       -5     
Flag Coverage Δ
suite.unit 80.41% <96.15%> (+1.26%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
packages/aws-cdk 80.41% <96.15%> (+1.26%) ⬆️

@aws-cdk-automation
Copy link
Collaborator

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

@@ -373,9 +373,9 @@ export async function makeConfig(): Promise<CliConfig> {
context: {
description: 'Manage cached context values',
options: {
reset: { alias: 'e', desc: 'The context key (or its index) to reset', type: 'string', requiresArg: true },
reset: { alias: 'e', desc: 'The context key (or its index) to reset', type: 'string', requiresArg: true, default: undefined },
Copy link
Contributor

Choose a reason for hiding this comment

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

Side note: we should probably change the codegen to always add an explicit default if none is provied.

Copy link
Contributor Author

Choose a reason for hiding this comment

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


constructor(...bags: Settings[]) {
this.bags = bags.length > 0 ? bags : [new Settings()];
constructor(...bags: ({name?: string; bag: Settings})[]) {
Copy link
Contributor

@mrgrain mrgrain Dec 19, 2024

Choose a reason for hiding this comment

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

❓ Don't think I'm wild about this API... Why are names optional?

I think eventually Context will be a public type and we need to revisit this API then.

Copy link
Contributor Author

@kaizencc kaizencc Dec 19, 2024

Choose a reason for hiding this comment

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

name is optional because one context bag we have comes from the CLI option, not a file. i should have called them filenames i guess

@mrgrain mrgrain added the pr/do-not-merge This PR should not be merged at this time. label Dec 19, 2024
Copy link
Contributor

@mrgrain mrgrain left a comment

Choose a reason for hiding this comment

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

Approved in principle with some minor comments for your consideration.

@kaizencc kaizencc added pr-linter/cli-integ-tested Assert that any CLI changes have been integ tested and removed pr/needs-cli-test-run This PR needs CLI tests run against it. labels Dec 19, 2024
@aws-cdk-automation aws-cdk-automation dismissed their stale review December 19, 2024 17:30

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

@kaizencc
Copy link
Contributor Author

@Mergifyio refresh

Copy link
Contributor

mergify bot commented Dec 20, 2024

refresh

✅ Pull request refreshed

@kaizencc kaizencc removed the pr/do-not-merge This PR should not be merged at this time. label Dec 20, 2024
Copy link
Contributor

mergify bot commented Dec 20, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 699fe73
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

mergify bot commented Dec 20, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 189bae3 into main Dec 20, 2024
16 of 17 checks passed
@mergify mergify bot deleted the conroy/refactor-commands branch December 20, 2024 15:09
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
contribution/core This is a PR that came from AWS. p2 pr-linter/cli-integ-tested Assert that any CLI changes have been integ tested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants