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

fix: add usage data metrics for codegen #13961

Merged
merged 3 commits into from
Oct 8, 2024

Conversation

bzsurbhi
Copy link

@bzsurbhi bzsurbhi commented Oct 7, 2024

Description of changes

  • Added a usageData metric for the codegen command
  • Added the word set in update secret command for auth
  • Updated the path to copy the source code from in functions

Description of how you validated changes

Tested in Beta, the metric getting generated successfully

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

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

@bzsurbhi bzsurbhi requested a review from a team as a code owner October 7, 2024 17:16
@@ -67,11 +71,15 @@ const generateGen2Code = async ({
};

const pipeline = createGen2Renderer(gen2RenderOptions);
const usageData = await getUsageDataMetric();

try {
await pipeline.render();
await analytics.logEvent('finishedMigration');
Copy link
Contributor

@abhi7cr abhi7cr Oct 7, 2024

Choose a reason for hiding this comment

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

nit: Should this be finishedCodegen and failedCodegen ?

@bzsurbhi bzsurbhi merged commit c18d6e6 into aws-amplify:migrations Oct 8, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants