amplify-cli
amplify-cli copied to clipboard
Published
20 hours ago •
aws-amplify
aws-amplify
I use the CLI and do an "amplify push" and it looks like it worked, but the "amplify status" shows that they are still local
Before opening, please confirm:
- [X] I have searched for duplicate or closed issues and discussions.
- [X] I have read the guide for submitting bug reports.
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
JavaScript Framework
Not applicable
Amplify APIs
Authentication, REST API, GraphQL API
Amplify Categories
No response
Environment information
# Put output below this line
System:
OS: macOS 12.6.7
CPU: (10) arm64 Apple M1 Pro
Memory: 7.22 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.0 - /usr/local/bin/node
npm: 8.1.0 - /usr/local/bin/npm
Browsers:
Chrome: 119.0.6045.105
Edge: 119.0.2151.46
Safari: 16.4.1
npmPackages:
@pierretrolle/words-counter: ^2.0.0 => 2.0.0
@vue/cli-plugin-babel: ~4.3.0 => 4.3.1
@vue/cli-plugin-eslint: ~4.3.0 => 4.3.1
@vue/cli-plugin-router: ~4.3.0 => 4.3.1
@vue/cli-plugin-vuex: ~4.3.0 => 4.3.1
@vue/cli-service: ~4.3.0 => 4.3.1
@vue/compiler-sfc: 2.7.14
aws-amplify: ^3.0.17 => 3.4.3
aws-amplify-vue: ^2.1.1 => 2.1.9
axios: ^0.19.2 => 0.19.2 (0.21.1)
babel-eslint: ^10.1.0 => 10.1.0
cheerio: ^1.0.0-rc.3 => 1.0.0-rc.12
core-js: ^3.6.4 => 3.30.1
eslint: ^6.7.2 => 6.8.0
eslint-plugin-vue: ^6.2.2 => 6.2.2
graphql: ^15.0.0 => 15.8.0 (14.0.0)
graphql-tag: ^2.12.6 => 2.12.6
request: ^2.88.2 => 2.88.2
require: ^2.4.20 => 2.4.20
testApp: 0.0.0
underscore: ^1.12.0 => 1.13.6
v-calendar: ^2.0.1 => 2.4.1
v-md-date-range-picker: ^2.6.0 => 2.6.0
vue: ^2.6.11 => 2.7.14 (2.6.11)
vue-meta: ^2.4.0 => 2.4.0
vue-router: ^3.1.6 => 3.6.5
vue-template-compiler: ^2.6.11 => 2.7.14
vue2-daterange-picker: ^0.6.1 => 0.6.8
vuewordcloud: ^18.7.12 => 18.7.12
vuex: ^3.1.3 => 3.6.2
npmGlobalPackages:
@aws-amplify/cli: 12.7.1
@vue/cli-service-global: 4.5.15
@vue/cli: 5.0.8
browserify: 17.0.0
corepack: 0.10.0
create-next-app: 13.4.3
http-server: 14.1.1
mapscii: 0.3.1
next: 13.4.3
npm: 8.1.0
pkg: 5.8.1
react-dom: 18.2.0
react: 18.2.0
rollup: 3.20.2
webpack-cli: 5.0.1
webpack: 5.78.0
Describe the bug
I am trying to make some changes and havent touched this project for a while. I made the changes locally and am trying to amplify push them up using the CLI. The changes appear to be successful, but when I amplify status I see them as still needing to be pushed up:
macbook-pro-3:amplifynewsscraper jameswolf$ amplify push
✔ Successfully pulled backend environment dev from the cloud.
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ Delete │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
✔ Are you sure you want to continue? (Y/n) · yes
The following types do not have '@auth' enabled. Consider using @auth with @model
- Scrape
- NewsArticle
- DailyWordCloudList
- Publisher
Learn more about @auth here: https://docs.amplify.aws/cli-legacy/graphql-transformer/auth
⚠️ Your instance type for OpenSearch is t2.small.elasticsearch, you may experience performance issues or data loss. Consider reconfiguring with the instructions here https://docs.amplify.aws/cli-legacy/graphql-transformer/searchable/
GraphQL schema compiled successfully.
Edit your schema at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema.graphql or place .graphql files in a directory at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types?
This will overwrite your current graphql queries, mutations and subscriptions Yes
Deploying resources into dev environment. This will take a few minutes. ⠹
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying funDeploying resources into dev environment. This will take a few minutes. ⠙
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/4
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying function externalapifunction [ ---------------------------------------- ] 0/4
Deploying function graphqllayer [ ---------------------------------------- ] 0/27
Deploying function newsarticlebuildwordcloud [ ---------------------------------------- ] 0/6
Deploying function newsarticlehydrate [ ---------------------------------------- ] 0/4
Deploying function newsarticlemainscrape [ ---------------------------------------- ] 0/4
Deploying function newsarticleprimaryscrape [ ---------------------------------------- ] 0/6
Deploying function newsarticlepublisherscrape [ ---------------------------------------- ] 0/6
Deploying function puppetfunction [ ---------------------------------------- ] 0/3
Deploying function testlayers [ ---------------------------------------- ] 0/4
✔ Done
Project Identifier: 6707b59117ca4c07d26880af30dad26e
(base) macbook-pro-3:amplifynewsscraper jameswolf$ amplify status
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ Delete │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
Expected behavior
I expect it to show an error on push if it fails so that I can see what the issue was, it seems instead to be doing some sort of soft failure and I dont know what to try next. I swear there is a flash of red text when it it pushing but it is so fast I cant make out what it is and it is gone. Please help, I am completely stuck
Reproduction steps
amplify push
amplify status
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
the app is still running fine, I am just stuck unable to make changes since I cannot push anything up
Hello, @contractorwolf 👋. I'm going to transfer this issue to our CLI repo for better assistance.
Hey @contractorwolf, thank you for reaching. On diving into the logs noticed the Cloudformation error Stack: is in UPDATE_ROLLBACK_FAILED state and can not be updated.. Could check the AWS Cloudformation console for any stack failure errors for the application?
Could you add --debug to the push command and provide us the output?
additionally, noticed the API update in the status. if the push runs into a similar error, could you check the S3 console, the applications deployment bucket for a deployment-state file, remove the file if exists and rerun the push command.
if I look at my stacks and set it to unnested I can see that my newsscraper one (this project) appears to be in an update rollback failed
if I dig further into the stack events and click the root cause button I see this:
But I dont see that as useful.
When I found that S3 bucket I see this:
but i dont see a deployment state file in that folder.
I ran push again with the --debug and it gave me this:
macbook-pro-3:amplifynewsscraper jameswolf$ amplify push --debug
Not pulling components because this project is not configured with the "react" framework.
⠧ Fetching updates to backend environment: dev from the cloud.Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
✔ Successfully pulled backend environment dev from the cloud.
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ Delete │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
✔ Are you sure you want to continue? (Y/n) · yes
The following types do not have '@auth' enabled. Consider using @auth with @model
- Scrape
- NewsArticle
- DailyWordCloudList
- Publisher
Learn more about @auth here: https://docs.amplify.aws/cli-legacy/graphql-transformer/auth
⚠️ Your instance type for OpenSearch is t2.small.elasticsearch, you may experience performance issues or data loss. Consider reconfiguring with the instructions here https://docs.amplify.aws/cli-legacy/graphql-transformer/searchable/
GraphQL schema compiled successfully.
Edit your schema at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema.graphql or place .graphql files in a directory at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
Overrides functionality is not implemented for this category
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types?
This will overwrite your current graphql queries, mutations and subscriptions Yes
Deploying resources into dev environment. This will take a few minutes. ⠋
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying resources into dev environment. This will take a few minutes. ⠙
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying resources into dev environment. This will take a few minutes. ⠹
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/4
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying function externalapifunction [ ---------------------------------------- ] 0/4
Deploying function graphqllayer [ ---------------------------------------- ] 0/27
Deploying function newsarticlebuildwordcloud [ ---------------------------------------- ] 0/6
Deploying function newsarticlehydrate [ ---------------------------------------- ] 0/4
Deploying function newsarticlemainscrape [ ---------------------------------------- ] 0/4
Deploying function newsarticleprimaryscrape [ ---------------------------------------- ] 0/6
Deploying function newsarticlepublisherscrape [ ---------------------------------------- ] 0/6
Deploying function puppetfunction [ ---------------------------------------- ] 0/3
Deploying function testlayers [ ---------------------------------------- ] 0/4
🛑 Stack:arn:aws:cloudformation:us-east-1:237169730438:stack/amplify-amplifynewsscraper-dev-231429/b20b50d0-98b5-11ea-aac6-0afe492705d7 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
DeploymentFault: Stack:arn:aws:cloudformation:us-east-1:237169730438:stack/amplify-amplifynewsscraper-dev-231429/b20b50d0-98b5-11ea-aac6-0afe492705d7 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
at Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-provider-awscloudformation/lib/push-resources.js:362:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:137:16
at async Promise.all (index 0)
at async providersPush (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:133:5)
at async AmplifyToolkit.pushResources (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/push-resources.js:107:13)
at async Object.executeAmplifyCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:194:9)
at async executePluginModuleCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:139:5)
at async executeCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:37:9)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:121:5)
Stack:arn:aws:cloudformation:us-east-1:237169730438:stack/amplify-amplifynewsscraper-dev-231429/b20b50d0-98b5-11ea-aac6-0afe492705d7 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
ValidationError: Stack:arn:aws:cloudformation:us-east-1:237169730438:stack/amplify-amplifynewsscraper-dev-231429/b20b50d0-98b5-11ea-aac6-0afe492705d7 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
at Request.extractError (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
at RequestDeploying resources into dev environment. This will take a few minutes. ⠼
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying funDeploying resources into dev environment. This will take a few minutes. ⠴
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠦
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠧
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠇
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠏
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠋
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠙
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠹
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠼
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying apiDeploying resources into dev environment. This will take a few minutes. ⠴
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/4
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying function externalapifunction [ ---------------------------------------- ] 0/4
Deploying function graphqllayer [ ---------------------------------------- ] 0/27
Deploying function newsarticlebuildwordcloud [ ---------------------------------------- ] 0/6
Deploying function newsarticlehydrate [ ---------------------------------------- ] 0/4
Deploying function newsarticlemainscrape [ ---------------------------------------- ] 0/4
Deploying function newsarticleprimaryscrape [ ---------------------------------------- ] 0/6
Deploying function newsarticlepublisherscrape [ ---------------------------------------- ] 0/6
Deploying function puppetfunction [ ---------------------------------------- ] 0/3
Deploying function testlayers [ ---------------------------------------- ] 0/4
✔ Done
Project Identifier: 6707b59117ca4c07d26880af30dad26e
any ideas on how to get this fixed? I dont know much about cloud formation? cal I just delete the stack or something? What is the issue?
Hey @contractorwolf, apologies for the delay in a response.
Could open the nested stack that failed on the Lambda function, the AWS Cloudformation console, the reason for failure should be in the stack events. The stack may have been deleted so do check the deleted stacks as well if you do not find it under the Active or failed.
When diving into the project noticed some information, the Auth resource seems to be utilizing yml file indicating the resource was not migrated. Does the Lambda function from the screenshot depend on the Auth resource?
To migrate the Auth resource, could you run amplify update auth which should provide a prompt to migrate the resource.
um, ok. I am using cognito with google federated, but I am not sure on which selection I need to choose:
@ykethan my guess would be update oauth? I want to go with the defaults but i need Federated fo my google login
@contractorwolf did the cli prompt to migrate the auth resource?
yes, select the Update OAuth social providers and re-enter the provider information, then run the push.
if this does not work, we could temporarily remove the providers then re-add the providers on the next push.
nope, still same issue. Looks like it worked but amplify status still shows unchanged items:
(base) macbook-pro-3:amplifynewsscraper jameswolf$ amplify update auth
Please note that certain attributes may not be overwritten if you choose to use defaults settings.
You have configured resources that might depend on this Cognito resource. Updating this Cognito resource could have unintended side effects.
Using service: Cognito, provided by: awscloudformation
What do you want to do? (Use arrow keys)
❯ Apply default configuration without Social Provider (Federation)
Walkthrough all the auth configurations
Add/Edit signin and signout redirect URIs
Update OAuth social providers
Create or update Cognito user pool groups
Create or update Admin queries API
* History restored
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
(base) macbook-pro-3:amplifynewsscraper jameswolf$
* History restored
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
(base) macbook-pro-3:amplifynewsscraper jameswolf$ amplify update auth
Please note that certain attributes may not be overwritten if you choose to use defaults settings.
You have configured resources that might depend on this Cognito resource. Updating this Cognito resource could have unintended side effects.
Using service: Cognito, provided by: awscloudformation
What do you want to do? Update OAuth social providers
Select the identity providers you want to configure for your user pool: Google
You've opted to allow users to authenticate via Google. If you haven't already, you'll need to go to https://developers.google.com/iden
tity and create an App ID.
Enter your Google Web Client ID for your OAuth flow:
Enter your Google Web Client Secret for your OAuth flow:
✅ Successfully updated auth resource amplifynewsscrapere0220fb9 locally
✅ Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
✅ Successfully updated resource update locally
✅ Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
(base) macbook-pro-3:amplifynewsscraper jameswolf$ amplify push
╭────────────────────────────────────────────────────────────╮
│ │
│ Update available: │
│ Run amplify upgrade for the latest features and fixes! │
│ │
╰────────────────────────────────────────────────────────────╯
✔ Successfully pulled backend environment dev from the cloud.
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ Delete │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
⚠️ Amplify CLI now supports verifying a Cognito user email address that has been changed and will automatically update your auth configuration. Read more: https://docs.amplify.aws/lib/auth/manageusers/q/platform/js/#updating-and-verifying-a-cognito-user-email-address
✔ Are you sure you want to continue? (Y/n) · yes
The following types do not have '@auth' enabled. Consider using @auth with @model
- Scrape
- NewsArticle
- DailyWordCloudList
- Publisher
Learn more about @auth here: https://docs.amplify.aws/cli-legacy/graphql-transformer/auth
⚠️ Your instance type for OpenSearch is t2.small.elasticsearch, you may experience performance issues or data loss. Consider reconfiguring with the instructions here https://docs.amplify.aws/cli-legacy/graphql-transformer/searchable/
GraphQL schema compiled successfully.
Edit your schema at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema.graphql or place .graphql files in a directory at /Users/jameswolf/Documents/Github/amplify/amplifynewsscraper/amplify/backend/api/amplifynewsscraper/schema
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types?
This will overwrite your current graphql queries, mutations and subscriptions Yes
Deploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying resources into dev environment. This will take a few minutes. ⠼
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying autDeploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/17
Deploying api amplifynewsscraper [ ---------------------------------------- ] 0/10
Deploying api newsapi [ ---------------------------------------- ] 0/5
Deploying api testerapi [ ---------------------------------------- ] 0/6
Deploying auth amplifynewsscrapere0220fb9 [ ---------------------------------------- ] 0/15
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/4
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying function externalapifunction [ ---------------------------------------- ] 0/4
Deploying function graphqllayer [ ---------------------------------------- ] 0/27
Deploying function newsarticlebuildwordcloud [ ---------------------------------------- ] 0/6
Deploying function newsarticlehydrate [ ---------------------------------------- ] 0/4
Deploying function newsarticlemainscrape [ ---------------------------------------- ] 0/4
Deploying function newsarticleprimaryscrape [ ---------------------------------------- ] 0/6
Deploying function newsarticlepublisherscrape [ ---------------------------------------- ] 0/6
Deploying function puppetfunction [ ---------------------------------------- ] 0/3
Deploying function testlayers [ ---------------------------------------- ] 0/4
✔ Done
Project Identifier: 6707b59117ca4c07d26880af30dad26e
(base) macbook-pro-3:amplifynewsscraper jameswolf$ amplify status
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ Delete │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
GraphQL endpoint:
GraphQL API KEY:
GraphQL transformer version: 1
REST API endpoint:
Hosted UI Endpoint:
Test Your Hosted UI Endpoint:
@ykethan I removed the clientID and the key from the content pasted above, but I had added them from the google console and it accepted the values as before, just didnt want them to show here, also removed the endpoints for safety, just FYI. Still looks like it went but still shows updated operations and delete operations pending. So the push didnt go even though there isnt an error displayed :/
@contractorwolf outside the existing application folder could you create a new empty folder and pull the Amplify app using amplify pull --appId <app-id> --envName dev, then run amplify status. Does this also a similar status? additionally, could you try making a small change such as adding a new line in a function and running push also show similar push behavior?
Additionally, installed cli appears to be on a older version, could can run amplify -v to get the local installed version.
I did that, copying my app Id from the aws console for that project. It reopens the aws console on that project and asks me to login again. When I choose "login with my aws account" from this popup (even though I am already logged in to my AWS account):
I get this error message:
FYI, I have never used amplify studio for any of my amplify projects. Anyway I appear to be stuck again since I cant download the project in a new location. I still have access to the project if I log in normally. How else can I get the CLI login key if I log in normally @ykethan?
@ykethan I finally got past that Studio application failed) by turning amplify studio of then back on again and deleting the amplify pull folder instance that it brought down (after I updated the CLI to the latest). It then alloweed me to pull the latest version of the backend code from the server into a temp folder locally. I updated my auth using amplify update auth, then made a small code change to one of my functions (updated the GPT model to the latest) and attempted to push just those changes up. Sort of looked like it worked (no shown errors) but checking the status still shows that the 2 changes are only local and did not get to the server:
(base) macbook-pro-3:temp jameswolf$ amplify push
✔ Successfully pulled backend environment dev from the cloud.
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
⚠️ Amplify CLI now supports verifying a Cognito user email address that has been changed and will automatically update your auth configuration. Read more: https://docs.amplify.aws/lib/auth/manageusers/q/platform/js/#updating-and-verifying-a-cognito-user-email-address
✔ Are you sure you want to continue? (Y/n) · yes
Deploying resources into dev environment. This will take a few minutes. ⠼
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/18
Deploying auth amplifynewsscrapere0220fb9 [ ---------------------------------------- ] 0/15
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/2
Deploying resources into dev environment. This will take a few minutes. ⠴
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/18
Deploying auth amplifynewsscrapere0220fb9 [ ---------------------------------------- ] 0/15
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/2
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying funDeploying resources into dev environment. This will take a few minutes. ⠸
Deploying root stack amplifynewsscraper [ ---------------------------------------- ] 0/18
Deploying auth amplifynewsscrapere0220fb9 [ ---------------------------------------- ] 0/15
Deploying function amplifynewsscraperscrapelayer [ ---------------------------------------- ] 0/2
Deploying function articleLinkService [ ---------------------------------------- ] 0/5
Deploying function externalapifunction [ ---------------------------------------- ] 0/4
Deploying function graphqllayer [ ---------------------------------------- ] 0/25
Deploying function newsarticlebuildwordcloud [ ---------------------------------------- ] 0/6
Deploying function newsarticlehydrate [ ---------------------------------------- ] 0/4
Deploying function newsarticlemainscrape [ ---------------------------------------- ] 0/4
Deploying function newsarticleprimaryscrape [ ---------------------------------------- ] 0/6
Deploying function newsarticlepublisherscrape [ ---------------------------------------- ] 0/6
Deploying function puppetfunction [ ---------------------------------------- ] 0/3
Deploying function repolayer [ ---------------------------------------- ] 0/18
Deploying function testlayers [ ---------------------------------------- ] 0/4
✔ Done
Project Identifier: 6707b59117ca4c07d26880af30dad26e
(base) macbook-pro-3:temp jameswolf$ amplify status
Current Environment: dev
┌──────────┬───────────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Auth │ amplifynewsscrapere0220fb9 │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ articleLinkService │ Update │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ amplifynewsscraper │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ newsapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Api │ testerapi │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ amplifynewsscraperscrapelayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ externalapifunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ graphqllayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlebuildwordcloud │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlehydrate │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlemainscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticleprimaryscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ newsarticlepublisherscrape │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ puppetfunction │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ repolayer │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Function │ testlayers │ No Change │ awscloudformation │
├──────────┼───────────────────────────────┼───────────┼───────────────────┤
│ Queue │ articleLinks │ No Change │ awscloudformation │
└──────────┴───────────────────────────────┴───────────┴───────────────────┘
(insert various expletives)!!!!
Help
@contractorwolf, it appears the CloudFormation is failing with <Stack> is in UPDATE_ROLLBACK_FAILED state and can not be updated.. would be open for a quick call. I am available on discord, my handle is ykethan
Thanks for trying out everything today @ykethan, here are the screenshots I promosed:
@contractorwolf apologies on the delay in a response. Cloudforamtion template should be in UPDATE_COMPLETE , could you try upgrading NodeJS on the Lambda functions and pushing this.
@contractorwolf wanted to follow up on this issue. were you able to upgrade the Lambda functions?
@contractorwolf could you check the Amplify stack on CloudFormation console if the stack are in a failed status. Do ensure the Amplify CLI has been updated to use the latest version. Then update the Lambda functions to use the supported NodeJs version and run amplify update auth to update the auth managed userpool client Lambda's.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}