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

chore(cli): refactor cli.ts to use CliArguments #32760

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from
Draft

Conversation

kaizencc
Copy link
Contributor

@kaizencc kaizencc commented Jan 6, 2025

To be written


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

@aws-cdk-automation aws-cdk-automation requested a review from a team January 6, 2025 22:19
@github-actions github-actions bot added the p2 label Jan 6, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jan 6, 2025
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 Jan 6, 2025
@aws-cdk-automation
Copy link
Collaborator

The pull request linter fails with the following errors:

❌ CLI code has changed. A maintainer must run the code through the testing pipeline (git fetch origin pull/32760/head && git push -f origin FETCH_HEAD:test-main-pipeline), then add the 'pr-linter/cli-integ-tested' label when the pipeline succeeds.

PRs must pass status checks before we can provide a meaningful review.

If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing Exemption Request and/or Clarification Request.

✅ A exemption request has been requested. Please wait for a maintainer's review.

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 8564109
  • Result: FAILED
  • Build Logs (available for 30 days)

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


/**
* The type of the assets to be garbage collected.
*
* @default 'all'
*/
readonly type: 's3' | 'ecr' | 'all';
readonly type: TypeType;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
readonly type: TypeType;
readonly type: AssetType;

@@ -1792,14 +1795,14 @@ export interface GarbageCollectionOptions {
*
* @default 'full'
*/
readonly action: 'print' | 'tag' | 'delete-tagged' | 'full';
readonly action: ActionType;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
readonly action: ActionType;
readonly action: GarbageCollectionAction;

Comment on lines +240 to +242
} else { // Skip bundling for all stacks
bundlingStacks = [];
}
Copy link
Contributor

Choose a reason for hiding this comment

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

The else is unnecessary if you assign bundlingStacks to the empty array earlier: let bundlingStacks = new Array<string>();

context[cxapi.BUNDLING_STACKS] = bundlingStacks;

debug('context:', context);

return context;
}

function setBundlingStacks(config: Configuration) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This works but is hard to parse for a human. In general I prefer this style:

// explain how this is even possible
if (!config.command) {
  return [];
}

const stackCommands = [...];

// command doesn't operate on a stack selection
if (!stackCommands.includes(config.command) {
  return [];
}

// If we deploy, diff, synth or watch a list of stacks exclusively we skip
// bundling for all other stacks.
if (config.settings.get(['exclusively']) && config.settings.get(['STACKS'])) {
  return config.settings.get(['STACKS']);
}

return ['**'];

Comment on lines +48 to +52
const configuration = new Configuration({
commandLineArguments: argv,
});
await configuration.load();
const settings = configuration.settings.all;
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: With that we still have the weird duplicity of having Configuration and Settings

Comment on lines +225 to 238
const diffOptions = settings.diff ?? {};
return cli.diff({
stackNames: args.STACKS,
exclusively: args.exclusively,
templatePath: args.template,
strict: args.strict,
contextLines: args.contextLines,
securityOnly: args.securityOnly,
fail: args.fail != null ? args.fail : !enableDiffNoFail,
stream: args.ci ? process.stdout : undefined,
compareAgainstProcessedTemplate: args.processed,
quiet: args.quiet,
changeSet: args['change-set'],
stackNames: diffOptions.STACKS ?? [],
exclusively: diffOptions.exclusively,
templatePath: diffOptions.template,
strict: diffOptions.strict,
contextLines: diffOptions.contextLines,
securityOnly: diffOptions.securityOnly,
fail: diffOptions.fail != null ? diffOptions.fail : !enableDiffNoFail,
stream: globalOptions.ci ? process.stdout : undefined,
compareAgainstProcessedTemplate: diffOptions.processed,
quiet: diffOptions.quiet,
changeSet: diffOptions.changeSet,
toolkitStackName: toolkitStackName,
Copy link
Contributor

Choose a reason for hiding this comment

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

This is good already, but ideally the next step would be a strongly typed helper function/method so we can do:

return cli.diff(diffSettingsToDiffOptions(settings.diff));

@aws-cdk-automation
Copy link
Collaborator

The pull request linter fails with the following errors:

❌ CLI code has changed. A maintainer must run the code through the testing pipeline (git fetch origin pull/32760/head && git push -f origin FETCH_HEAD:test-main-pipeline), then add the 'pr-linter/cli-integ-tested' label when the pipeline succeeds.

PRs must pass status checks before we can provide a meaningful review.

If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing Exemption Request and/or Clarification Request.

✅ A exemption request has been requested. Please wait for a maintainer's review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS. p2 pr/needs-cli-test-run This PR needs CLI tests run against it.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants