search

aws-samples / iam-identity-center-team

Open-source temporary elevated access solution for AWS IAM Identity Center.
https://aws-samples.github.io/iam-identity-center-team/
MIT No Attribution
305 stars 76 forks source link

Reinstalling TEAM Build Issues #21

Closed gambol99 closed 1 year ago

gambol99 commented 1 year ago

Describe the bug

Some background. We had the TEAM application up and running in an new AWS Organization. We needed at one point to switch our Identity Center to "auto provisioning" to sync our users and groups withe Gsuite (ssosync). The TEAM application at that point disappeared from the Identity Center login page.

We were changing groups, so figured it was best to ./destroy.sh and recreate the Team application later. After getting ssosync up and running, we deleted the s3 buckets (associates to team), removed the application (identity center) and hopefully had a clean install; All the cloudformation stacks associated to team had been removed by the ./destroy.sh.

We then followed the install guide again, but this time was met with the following in the build stage of the Amplify application.

I'm not sure if this is related to something left behind, an issue with auto provisioning or an actual bug though

2023-06-27T07:55:51.081Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-27T07:55:51.126Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamRouter-C0aiEXuv
2023-06-27T07:55:51.148Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/python-5t5zfKw8
2023-06-27T07:55:51.166Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamListGroups-JcYy4m3j
2023-06-27T07:55:51.182Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamgetGroups-m0D2cjJL
2023-06-27T07:55:51.211Z [INFO]: Installing dependencies from Pipfile.lock (2a8f7d)...
2023-06-27T07:55:51.217Z [INFO]: Installing dependencies from Pipfile.lock (a04e88)...
2023-06-27T07:55:51.245Z [INFO]: Installing dependencies from Pipfile.lock (6974cb)...
2023-06-27T07:55:51.282Z [INFO]: Installing dependencies from Pipfile.lock (2a8f7d)...
2023-06-27T07:55:52.612Z [WARNING]: created virtual environment CPython3.8.0.final.0-64 in 2203ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/teamgetMgmtAccountDetails-0CDMFsyW, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-27T07:55:52.617Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-27T07:55:52.664Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-27T07:55:52.673Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-27T07:55:52.693Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-27T07:55:52.724Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamgetMgmtAccountDetails-0CDMFsyW
2023-06-27T07:55:52.829Z [INFO]: Installing dependencies from Pipfile.lock (e02f68)...
2023-06-27T07:55:52.933Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-27T07:55:53.660Z [WARNING]: ✖ There was an error initializing your environment.
2023-06-27T07:55:53.661Z [INFO]: 🛑 Command failed with exit code 1: pipenv install
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2023-06-27T07:55:53.744Z [INFO]: 
2023-06-27T07:55:53.744Z [INFO]: Session Identifier: a22255ec-bacd-49b4-a323-74e8b0cf9c17
2023-06-27T07:55:53.809Z [ERROR]: !!! Build failed
2023-06-27T07:55:53.809Z [ERROR]: !!! Non-Zero Exit Code detected
2023-06-27T07:55:53.809Z [INFO]: # Starting environment caching...
2023-06-27T07:55:53.810Z [INFO]: # Environment caching completed
Terminating logging...

To Reproduce See above

Expected behavior Destroy and reinstall

Screenshots NA

Desktop (please complete the following information): NA

Smartphone (please complete the following information): NA

Additional context Add any other context about the problem here.

EGHPrometeia commented 1 year ago

I've got the same problem, except I am not running destroy.sh beforehand. I'm redeploying the app from the management console ("redeploy this version" button)

tawoyinfa commented 1 year ago

@EGHPrometeia is your case the same ? Have you also switched to SCIM automatic provisioning ? did you make any changes to the code ?

@gambol99 I reckon the reason the TEAM app appeared to have disappeared in IdC is because the groups and user assignment to the application was deleted after you changed your SCIM profile. I havent come across the issue you have described when reInstalling. can you share the structure of the 'teamgetMgmtAccountDetails' function folder. Share the full build output as well.

gambol99 commented 1 year ago

Hi @tawoyinfa

Thanks the quick response .. I've attached the logs

log.txt

Forgive my stupidity :-) when you say the structure of the teamgetMgmtAccountDetails function folder. .. Do you mean from within the repo?? 

[jest@starfury teamgetMgmtAccountDetails]$ pwd
/home/jest/scm/codecommit/team-idc-app/amplify/backend/function/teamgetMgmtAccountDetails
[jest@starfury teamgetMgmtAccountDetails]$ tree
.
├── amplify.state
├── custom-policies.json
├── function-parameters.json
├── Pipfile
├── Pipfile.lock
├── src
│   ├── event.json
│   ├── index.py
│   └── setup.py
└── teamgetMgmtAccountDetails-cloudformation-template.json

2 directories, 9 files

Or is something uploaded else where, which i can grab ..

Texas-Tim commented 1 year ago

Hello, I also ran into an issue with my deployment where it wasn't logging in as I expected so I decided to just do a clean install to see if that fixed the problem. After making sure that all resources were removed, I performed the typical new installation steps and came across this error.

tawoyinfa commented 1 year ago

Looks like there is a problem with the Amplify build. We are currently looking into and would provide an update as soon as it is fixed

rapides commented 1 year ago

@tawoyinfa I have raised the same issue in post #23, and I am eagerly anticipating your response and update. Thanks!

tawoyinfa commented 1 year ago

It looks like there is an issue with the latest version of pipenv(2023.6.26) which is used by the Amplify build pipeline to package the backend python lambda functions. I have updated the buildspec to use the most recent stable version of pipenv(2023.6.12). Try deploying the latest commit(d440596) and let me know if it fixes the problem for you all.

gambol99 commented 1 year ago

Hi @tawoyinfa ... confirmed i'm no longer receiving the error and the application is rolling out as i type :-) ... I'll let the other's confirm but for me it looks fixed ... Thank you kindly!! ... and awesome app by the way, would it be great to see it as a feature of Identity Center one day ..

rapides commented 1 year ago

Unfortunately, it is still failing for me but on a different step - see #24 . @gambol99 you don't have this issue?

gambol99 commented 1 year ago

Hi @rapides .. so the install was successful, but i'm hitting a different issue .. Note the difference between our installs here (looking at the logs you got in #24) was I'm not installing in the management account - I had delegated admin of Identity Center to another account

@tawoyinfa Post install we setup Identity Center and Cognito integrations as per install guide and logged in .. We then created a single Eligibility policy which permitted access without approval required to a collection of OU's for testing purposes .. Under My Requests a request made status moves from pending to approved and the session is listed under Elevated Access as in-progress ... But no actual role appears in the SSO portal for me to click on

I've tried to look for error logs within CloudWatch, but didn't stumble on anything obvious - what is the LogGroup I should be looking at?

rapides commented 1 year ago

@gambol99 I'm not installing it on the management account either. I use a separate AWS account to install TEAM on it.

tawoyinfa commented 1 year ago

@gambol99 the best place to troubleshoot this would be the stepfunction logs. I will suggest you check the TEAM-GRANT-SM workflow output to see if there was any error. @rapides is your installation working as expected or do you have the same issue as @gambol99 ?

rapides commented 1 year ago

@tawoyinfa Nope, it's working fine on my end. 👍🏻

gambol99 commented 1 year ago

@gambol99 the best place to troubleshoot this would be the stepfunction logs. I will suggest you check the TEAM-GRANT-SM workflow output to see if there was any error. @rapides is your installation working as expected or do you have the same issue as @gambol99 ?

thank you kindly @tawoyinfa ... It was an SES issue, I verified the domain and it all worked again ... I'm gonna mark the issue as fixed

EGHPrometeia commented 1 year ago

@tawoyinfa

Hi and sorry for the delay. I integrated your last commit (pipenv==2023.6.12) on my CodeCommit repo and the Continuous Deployment starts executing. Nevertheless, I encounter the same error as before. Hereby are my logs: 

2023-06-29T08:47:51.628Z [INFO]: # Checking for Git submodules at: /codebuild/output/src3529162256/src/team-idc-app/.gitmodules
2023-06-29T08:47:51.636Z [INFO]: # Retrieving environment cache...
2023-06-29T08:47:51.674Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2023-06-29T08:47:51.674Z [INFO]: ---- Setting Up SSM Secrets ----
2023-06-29T08:47:51.675Z [INFO]: SSM params {"Path":"/amplify/d11z1jiw7e1fot/prod/","WithDecryption":true}
2023-06-29T08:47:51.738Z [INFO]: No live updates for this build run
2023-06-29T08:47:51.741Z [INFO]: # Retrieving cache...
2023-06-29T08:47:51.763Z [INFO]: # Retrieved cache
2023-06-29T08:48:26.766Z [INFO]: ## Starting Backend Build
                                 # Starting phase: preBuild
                                 # Executing command: npm i -g @aws-amplify/cli@10.7.3
2023-06-29T08:48:42.319Z [INFO]: changed 26 packages, and audited 27 packages in 15s
2023-06-29T08:48:42.322Z [INFO]: 7 packages are looking for funding
                                 run `npm fund` for details
                                 found 0 vulnerabilities
2023-06-29T08:48:42.329Z [INFO]: # Executing command: node parameters.js
2023-06-29T08:48:42.361Z [INFO]: updating stepfunctions custom parameters"...
2023-06-29T08:48:42.362Z [INFO]: updating amplify config for branch "prod"...
2023-06-29T08:48:42.364Z [INFO]: updating react parameters"...
2023-06-29T08:48:42.364Z [INFO]: updating teamgetgroups lambda parameters"...
2023-06-29T08:48:42.367Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
2023-06-29T08:48:42.367Z [INFO]: # Executing command: npm i -S graphql-ttl-transformer
2023-06-29T08:48:55.566Z [WARNING]: npm
2023-06-29T08:48:55.568Z [WARNING]: WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
                                    npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
2023-06-29T08:48:55.852Z [WARNING]: npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
2023-06-29T08:48:56.093Z [WARNING]: npm WARN deprecated
2023-06-29T08:48:56.093Z [WARNING]: resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
2023-06-29T08:48:56.233Z [WARNING]: npm WARN
2023-06-29T08:48:56.233Z [WARNING]: deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
2023-06-29T08:48:56.594Z [WARNING]: npm WARN deprecated
2023-06-29T08:48:56.594Z [WARNING]: querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
2023-06-29T08:48:56.694Z [WARNING]: npm WARN
2023-06-29T08:48:56.694Z [WARNING]: deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
2023-06-29T08:48:56.876Z [WARNING]: npm WARN
2023-06-29T08:48:56.876Z [WARNING]: deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2023-06-29T08:48:57.160Z [WARNING]: npm WARN
2023-06-29T08:48:57.160Z [WARNING]: deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
2023-06-29T08:48:57.203Z [WARNING]: npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
2023-06-29T08:48:58.560Z [WARNING]: npm WARN deprecated
2023-06-29T08:48:58.560Z [WARNING]: workbox-cacheable-response@6.6.0: workbox-background-sync@6.6.0
2023-06-29T08:49:00.025Z [WARNING]: npm WARN
2023-06-29T08:49:00.027Z [WARNING]: deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
2023-06-29T08:49:40.020Z [INFO]: added 3103 packages, and audited 3122 packages in 57s
2023-06-29T08:49:40.026Z [INFO]: 260 packages are looking for funding
                                 run `npm fund` for details
2023-06-29T08:49:40.267Z [INFO]: 115 vulnerabilities (11 low, 104 moderate)
                                 To address issues that do not require attention, run:
                                 npm audit fix
                                 To address all issues possible (including breaking changes), run:
                                 npm audit fix --force
                                 Some issues need review, and may require choosing
                                 a different dependency.
                                 Run `npm audit` for details.
2023-06-29T08:49:40.296Z [INFO]: # Executing command: update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.9 11
2023-06-29T08:49:40.513Z [INFO]: # Executing command: /usr/local/bin/pip3.9 install --user pipenv
2023-06-29T08:49:42.930Z [INFO]: Collecting pipenv
2023-06-29T08:49:42.986Z [INFO]: Downloading pipenv-2023.6.26-py3-none-any.whl (2.8 MB)
2023-06-29T08:49:43.348Z [INFO]: Collecting virtualenv>=20.17.1
2023-06-29T08:49:43.353Z [INFO]: Downloading virtualenv-20.23.1-py3-none-any.whl (3.3 MB)
2023-06-29T08:49:43.485Z [INFO]: Collecting virtualenv-clone>=0.2.5
2023-06-29T08:49:43.491Z [INFO]: Downloading virtualenv_clone-0.5.7-py3-none-any.whl (6.6 kB)
2023-06-29T08:49:43.502Z [INFO]: Requirement already satisfied: certifi in /usr/local/lib/python3.9/site-packages (from pipenv) (2022.12.7)
2023-06-29T08:49:43.888Z [INFO]: Collecting setuptools>=67.0.0
2023-06-29T08:49:43.920Z [INFO]: Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
2023-06-29T08:49:44.066Z [INFO]: Collecting platformdirs<4,>=3.5.1
2023-06-29T08:49:44.092Z [INFO]: Downloading platformdirs-3.8.0-py3-none-any.whl (16 kB)
2023-06-29T08:49:44.164Z [INFO]: Collecting filelock<4,>=3.12
2023-06-29T08:49:44.200Z [INFO]: Downloading filelock-3.12.2-py3-none-any.whl (10 kB)
2023-06-29T08:49:44.258Z [INFO]: Collecting distlib<1,>=0.3.6
2023-06-29T08:49:44.266Z [INFO]: Downloading distlib-0.3.6-py2.py3-none-any.whl (468 kB)
2023-06-29T08:49:45.534Z [INFO]: Installing collected packages: platformdirs, filelock, distlib, virtualenv, virtualenv-clone, setuptools, pipenv
2023-06-29T08:49:47.937Z [INFO]: Successfully installed distlib-0.3.6 filelock-3.12.2 pipenv-2023.6.26 platformdirs-3.8.0 setuptools-68.0.0 virtualenv-20.23.1 virtualenv-clone-0.5.7
2023-06-29T08:49:48.254Z [WARNING]: WARNING: You are using pip version 20.2.3; however, version 23.1.2 is available.
                                    You should consider upgrading via the '/usr/local/bin/python3.9 -m pip install --upgrade pip' command.
2023-06-29T08:49:49.653Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2023-06-29T08:49:50.403Z [INFO]: Amplify AppID found: d11z1jiw7e1fot. Amplify App name is: TEAM-IDC-APP
2023-06-29T08:49:50.459Z [INFO]: Adding backend environment prod to AWS Amplify app: d11z1jiw7e1fot
2023-06-29T08:49:55.961Z [INFO]: 
2023-06-29T08:49:55.965Z [INFO]: CREATE_IN_PROGRESS amplify-teamidcapp-prod-84950 AWS::CloudFormation::Stack Thu Jun 29 2023 08:49:50 GMT+0000 (Coordinated Universal Time) User Initiated
                                 CREATE_IN_PROGRESS UnauthRole                    AWS::IAM::Role             Thu Jun 29 2023 08:49:53 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS AuthRole                      AWS::IAM::Role             Thu Jun 29 2023 08:49:53 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS DeploymentBucket              AWS::S3::Bucket            Thu Jun 29 2023 08:49:53 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS AuthRole                      AWS::IAM::Role             Thu Jun 29 2023 08:49:54 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
                                 CREATE_IN_PROGRESS UnauthRole                    AWS::IAM::Role             Thu Jun 29 2023 08:49:54 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
                                 CREATE_IN_PROGRESS DeploymentBucket              AWS::S3::Bucket            Thu Jun 29 2023 08:49:54 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2023-06-29T08:50:10.987Z [INFO]: 
2023-06-29T08:50:10.989Z [INFO]: CREATE_COMPLETE AuthRole   AWS::IAM::Role Thu Jun 29 2023 08:50:09 GMT+0000 (Coordinated Universal Time)
                                 CREATE_COMPLETE UnauthRole AWS::IAM::Role Thu Jun 29 2023 08:50:09 GMT+0000 (Coordinated Universal Time)
2023-06-29T08:50:20.998Z [INFO]: 
2023-06-29T08:50:21.337Z [INFO]: 
2023-06-29T08:50:21.375Z [WARNING]: - Uploading files.
2023-06-29T08:50:21.388Z [INFO]: 
2023-06-29T08:50:21.388Z [INFO]: 
2023-06-29T08:50:21.426Z [INFO]: 
2023-06-29T08:50:21.426Z [INFO]: 
2023-06-29T08:50:21.427Z [WARNING]: - Uploading files.
2023-06-29T08:50:21.874Z [WARNING]: - Initializing your environment: prod
2023-06-29T08:50:21.933Z [WARNING]: - Building resource api/team
2023-06-29T08:50:39.066Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:39.068Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:39.210Z [INFO]: ⚠️ WARNING: owners may reassign ownership for the following model(s) and role(s): requests: [owner, approver_ids], sessions: [owner, username, approver_ids]. If this is not intentional, you may want to apply field-level authorization rules to these fields. To read more: https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access.
2023-06-29T08:50:40.331Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/api/team/schema.graphql or place .graphql files in a directory at /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/api/team/schema
2023-06-29T08:50:40.332Z [WARNING]: - Building resource auth/team06dbb7fc
2023-06-29T08:50:40.475Z [WARNING]: - Building resource auth/userPoolGroups
2023-06-29T08:50:40.598Z [WARNING]: - Building resource custom/appsyncCloudwatchLogRole
2023-06-29T08:50:40.599Z [WARNING]: - Building custom resources
2023-06-29T08:50:40.602Z [WARNING]: - Building resource custom/cloudtrailLake
2023-06-29T08:50:40.602Z [WARNING]: - Building custom resources
2023-06-29T08:50:40.604Z [WARNING]: - Building resource custom/s3bucketSecurity
2023-06-29T08:50:40.604Z [WARNING]: - Building custom resources
2023-06-29T08:50:40.606Z [WARNING]: - Building resource custom/stepfunctions
2023-06-29T08:50:40.606Z [WARNING]: - Building custom resources
2023-06-29T08:50:40.610Z [WARNING]: ✔ Initialized provider successfully.
2023-06-29T08:50:40.933Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:40.933Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:40.933Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:40.933Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:40.934Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2023-06-29T08:50:41.029Z [INFO]: ⚠️ WARNING: owners may reassign ownership for the following model(s) and role(s): requests: [owner, approver_ids], sessions: [owner, username, approver_ids]. If this is not intentional, you may want to apply field-level authorization rules to these fields. To read more: https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access.
2023-06-29T08:50:41.951Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/api/team/schema.graphql or place .graphql files in a directory at /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/api/team/schema
2023-06-29T08:50:41.953Z [INFO]: 
2023-06-29T08:50:41.953Z [INFO]: Suggested configuration for new layer versions:
2023-06-29T08:50:41.953Z [INFO]: 
2023-06-29T08:50:41.955Z [INFO]: teamapplicationboto3layer
                                   - Description: Updated layer version  2023-06-29T08:50:41.953Z
2023-06-29T08:50:41.955Z [INFO]: 
2023-06-29T08:50:48.869Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.885Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.890Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.895Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.899Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.908Z [WARNING]: - Uploading files.
2023-06-29T08:50:48.968Z [WARNING]: - Uploading files.
2023-06-29T08:50:54.350Z [WARNING]: Creating a virtualenv for this project...
                                    Pipfile: /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/function/teamRouter/Pipfile
2023-06-29T08:50:54.367Z [WARNING]: Creating a virtualenv for this project...
2023-06-29T08:50:54.368Z [WARNING]: Pipfile: /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/function/teamgetGroups/Pipfile
2023-06-29T08:50:54.384Z [WARNING]: Using /usr/local/bin/python3.9 (3.9.0) to create virtualenv...
2023-06-29T08:50:54.402Z [WARNING]: Using /usr/local/bin/python3.9 (3.9.0) to create virtualenv...
2023-06-29T08:50:54.440Z [WARNING]: Creating a virtualenv for this project...
2023-06-29T08:50:54.441Z [WARNING]: Pipfile: /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/function/teamapplicationboto3layer/lib/python/Pipfile
2023-06-29T08:50:54.452Z [WARNING]: Creating a virtualenv for this project...
                                    Pipfile: /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/function/teamgetMgmtAccountDetails/Pipfile
2023-06-29T08:50:54.455Z [WARNING]: Creating a virtualenv for this project...
2023-06-29T08:50:54.455Z [WARNING]: Pipfile: /codebuild/output/src3529162256/src/team-idc-app/amplify/backend/function/teamListGroups/Pipfile
2023-06-29T08:50:54.472Z [WARNING]: Using /usr/local/bin/python3.9 (3.9.0) to create virtualenv...
2023-06-29T08:50:54.489Z [WARNING]: Using /usr/local/bin/python3.8 (3.8.0) to create virtualenv...
2023-06-29T08:50:54.504Z [WARNING]: Using /usr/local/bin/python3.9 (3.9.0) to create virtualenv...
2023-06-29T08:50:55.493Z [WARNING]: created virtual environment CPython3.9.0.final.0-64 in 698ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/teamRouter-UjaQm3YT, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-29T08:50:55.500Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-29T08:50:55.547Z [WARNING]: created virtual environment CPython3.9.0.final.0-64 in 648ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/teamgetGroups-kt_NGRCE, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-29T08:50:55.553Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-29T08:50:55.610Z [WARNING]: created virtual environment CPython3.9.0.final.0-64 in 742ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/python-qJxUDhoW, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-29T08:50:55.613Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamgetGroups-kt_NGRCE
2023-06-29T08:50:55.616Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-29T08:50:55.616Z [WARNING]: created virtual environment CPython3.9.0.final.0-64 in 616ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/teamListGroups-2CWooJJ0, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-29T08:50:55.622Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-29T08:50:55.650Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamRouter-UjaQm3YT
2023-06-29T08:50:55.693Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/python-qJxUDhoW
2023-06-29T08:50:55.718Z [INFO]: Installing dependencies from Pipfile.lock (2a8f7d)...
2023-06-29T08:50:55.739Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamListGroups-2CWooJJ0
2023-06-29T08:50:55.748Z [INFO]: Installing dependencies from Pipfile.lock (a04e88)...
2023-06-29T08:50:55.777Z [INFO]: Installing dependencies from Pipfile.lock (6974cb)...
2023-06-29T08:50:55.835Z [INFO]: Installing dependencies from Pipfile.lock (2a8f7d)...
2023-06-29T08:50:56.820Z [WARNING]: created virtual environment CPython3.8.0.final.0-64 in 1711ms
                                    creator CPython3Posix(dest=/root/.local/share/virtualenvs/teamgetMgmtAccountDetails-e9O4edy-, clear=False, no_vcs_ignore=False, global=False)
                                    seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
                                    added seed packages: pip==23.1.2, setuptools==67.8.0, wheel==0.40.0
                                    activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
2023-06-29T08:50:56.826Z [WARNING]: ✔ Successfully created virtual environment!
2023-06-29T08:50:56.937Z [WARNING]: Virtualenv location: /root/.local/share/virtualenvs/teamgetMgmtAccountDetails-e9O4edy-
2023-06-29T08:50:56.951Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-29T08:50:56.957Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-29T08:50:56.988Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-29T08:50:57.075Z [INFO]: Installing dependencies from Pipfile.lock (e02f68)...
2023-06-29T08:50:57.188Z [WARNING]: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
                                    or: setup.py --help [cmd1 cmd2 ...]
                                    or: setup.py --help-commands
                                    or: setup.py cmd --help
                                    error: invalid command 'egg_info'
2023-06-29T08:50:58.410Z [WARNING]: ✖ There was an error initializing your environment.
2023-06-29T08:50:58.417Z [INFO]: 🛑 Command failed with exit code 1: pipenv install
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2023-06-29T08:50:58.501Z [INFO]: 
2023-06-29T08:50:58.503Z [INFO]: Session Identifier: 43cc7b8a-f829-414e-86e2-47ee5007d12c
2023-06-29T08:50:58.576Z [ERROR]: !!! Build failed
2023-06-29T08:50:58.576Z [ERROR]: !!! Non-Zero Exit Code detected
2023-06-29T08:50:58.576Z [INFO]: # Starting environment caching...
2023-06-29T08:50:58.577Z [INFO]: # Environment caching completed
Terminating logging...
tawoyinfa commented 1 year ago

@EGHPrometeia Integrate the latest commit c4b779b and let me know if it fixes your problem

tawoyinfa commented 1 year ago

@rapides @gambol99 @EGHPrometeia we'd love to hear from you. Please complete this nonobligatory feedback form. Thank you for helping us improve!

EGHPrometeia commented 1 year ago

Thank you @tawoyinfa for the kind support.

I integrated the commits d440596 and c4b779b and pushed them on the CodeCommit repo. The deployment on Amplify started automatically anew but unfortunately keeps failing on the build stage.

I'll try to destroy the app and deploy it again and see if the problem still persists.

EGHPrometeia commented 1 year ago

The app has now successfully deployed thanks to the new commits. Thanks!