-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with New AWS CodeCommit Customers #336
Comments
Yes - just discovered this hitch when trying to get deployed! |
did any of you successfully deploy the application? i am actually stuck at the same build error because of codecommit. |
Yes - I got it working by making a clone in our own GitLab repo, and configuring a token in Secrets Manager to access it instead. |
I tried the same, but it doesn't work for me, I added the projected to my repo and modified the template.yaml with the below entry and referenced the URL. |
So, I also commented out the AWS CodeCommit part from the project and used GitHub in the template file. Here is the working reference for it: AmplifyApp:
Type: "AWS::Amplify::App"
Properties:
Name: TEAM-IDC-APP
AccessToken: <GITHUB_PAT_HERE>
Repository: !Sub https://github.com/<ORG_NAME>/<REPO-NAME>.git
Description: Temporary Elevated Access Management Application |
@CloudNinjaDev: It’s not working for me. Can you please provide more details? |
Description
AWS CodeCommit is no longer available to new customers. As a result, users who were not using CodeCommit before this change can no longer deploy the AWS TEAM application.
Steps to Reproduce
Attempt to deploy the AWS TEAM application as a new AWS customer.
I'm afraid it's an issue due to the unavailability of AWS CodeCommit.
Expected Behavior
The deployment process should provide flexibility to select a source code provider other than CodeCommit. Specifically, the parameters.sh file should include an option to configure the source code provider, rather than being restricted to CodeCommit.
Screenshots
The text was updated successfully, but these errors were encountered: