Questions tagged with Amazon CodeCatalyst
Content language: English
Sort by most recent
I could not figure out where does the source repository code in CodeCatalyst live, is it in S3 (couldn't found there)? where could I find it? does it really use CodeCommit behind the scene, couldn't find anything in CodeCommit related to CodeCatalyst repositories?
Could we use the repositories created in CodeCommit in the CodeCatalyst or vice versa?
I am looking forward to hear answers.
Thanks,
I realise CodeCatalyst is in preview, but it would be really useful if the API could be expanded so that we can manage issues via the CLI.
As an example, I'm thinking that it would be useful for a workflow to be able to raise an issue if there was a problem with a new run, and assign it to the author of the associated commit.
This could also provide a solution to my request for manual authorisation as part of a workflow - i.e. before deploying to prod, check if a ticket exists to approve the deployment, if not create one, and if one does exist, wait until it is closed by someone in a list. This would mean we need be able to
* query if a issue exists based on id, associated commit id, or other criteria. If the issue does exists, the details of the ticket, including the issue status should be returned
* create a query
asked 10 days ago
Can we restrict that the invited member email must of be of an specific organization @organization.com to let them access to that project?
Thanks,
what I know that on project level, CodeCatalyst provides only 2 roles; Contributor and Project administrator. I think Contributor has almost same access as of administrator except few things(can not remove project, invite other members, etc). Is there any way that we can restrict the invited member to not be able to run the workflow or could restrict them to perform certain actions (eg; create issue, merge pull request etc)?
Thanks,
I created a project using the blueprint of serverless image handler; deployment region set to 'us-east-1' and region for the bucket of cloudformation template 'us-east-1'. On running the 'build-and-deployOSS', I am getting error 'The action configuration is not valid'.
Those are the configuration steps defined in that workflow
Configuration:
Steps:
- Run: curl -O https://bootstrap.pypa.io/get-pip.py
- Run: python3 get-pip.py
- Run: yum install zip rsync -y
- Run: pip install --upgrade pip
- Run: pip install --upgrade setuptools
- Run: pip install --upgrade virtualenv
- Run: export OPS_CO_PATH=`pwd`
- Run: echo $OPS_CO_PATH
- Run: cd $OPS_CO_PATH/deployment
- Run: echo $OPS_CO_PATH/deployment
- Run: if ! aws s3api head-bucket --bucket $IMAGEBUCKET 2>/dev/null; then aws s3 mb s3://$IMAGEBUCKET --region $REGION; fi
- Run: if ! aws s3api head-bucket --bucket $TEMPLATE_OUTPUT_BUCKET 2>/dev/null; then aws s3 mb s3://$TEMPLATE_OUTPUT_BUCKET --region $TEMPLATE_REGION; fi
- Run: if ! aws s3api head-bucket --bucket $BUCKET_PREFIX-$REGION 2>/dev/null; then aws s3 mb s3://$BUCKET_PREFIX-$REGION --region $REGION; fi
- Run: ./build-s3-dist.sh $BUCKET_PREFIX $SOLUTION_NAME $VERSION >buildresults.txt
- Run: aws s3 cp $OPS_CO_PATH/deployment/global-s3-assets s3://$TEMPLATE_OUTPUT_BUCKET/$SOLUTION_NAME/$VERSION --recursive --acl bucket-owner-full-control
- Run: aws s3 cp $OPS_CO_PATH/deployment/regional-s3-assets s3://$BUCKET_PREFIX-$REGION/$SOLUTION_NAME/$VERSION --recursive --acl bucket-owner-full-control
I noticed that on build-s3-dist.sh file there is variable DIST_OUTPUT_BUCKET which is not in the templateParameters.json and also not listed as variables for that build. I tried to update the workflow by defining this variable and setting its value same as of 'TEMPLATE_OUTPUT_BUCKET' for the action 'build-and-deployOSS' (not sure what I did was right or not), and run that workflow again but getting error on that same step.
Any idea how this error could be fixed?
Thanks,
when I assign someone for issue that assignee don't get email for it. is it intentional? I guess assignee should receive email in that case
I have the project created with blueprint of SPA (react). I have CodeCatalyst successfully connected to dev environment (VSCode). SSH configs were updated via the extension 'Remote SSH'. When I run 'npm start', it gives me error 'sh: react-scripts: command not found'.
Any idea why its so?
I am using Free tier account. On creating a project with blueprint of SPA (framework: React, hosting: CloudFront + S3, CDK language: Typescript, region: us-west-2), it doesn't create any environment and result in 2 errors (missing Environment name) in one of the Workflow action.
does it happen because I am using free tier account?
My understanding is that CodeCatalyst uses the existing code* tools behind the scenes - is there anyway to access the codebuild badge functionality?
asked 14 days ago
One of my repos uses git submodules - but I can't see any method to perform a recursive clone as part of a workflow, other than adding a step in the workflow to run `git submodules init` and then a `git submodule update`.
Is there any method to define that a recursive clone is needed on checkout to the workflow?
asked 14 days ago
I deleted a space several days ago from within CodeCatalyst. I also made sure that it was deleted from the associated AWS account.
I've tried to create a new space using that same name, but CodeCatalyst tells me that the `Space name is already taken`.
Do I need to carry out some other action to make the name available again?
asked 15 days ago
Apologies for the length on this - tl;dr is that in builder ID A I can't create an AWS space and associate a billing account, but switching to builder ID B allows me to create an AWS space and use the same AWS account for billing successfully.
A couple of months ago I posted that I couldn't create an alias in CodeCatalyst for a new builder ID (ID A)(https://repost.aws/questions/QUbeV0idyfTuGVG-FmnzLS0Q/cant-create-alias-in-codecatalyst) and that I'd had to create an alternate builder ID (ID B) with a different email address which did work. It was suggested that validation around the alias was possibly a little 'aggressive', and sure enough after a couple of weeks I could create an alias and I was offered the option to create a CodeCatalyst space.
However, because I had the 2nd builder ID (B) setup I just continued using that and all worked well.
Today, I wanted to switch to using the original builder ID (A) since I now had the option, so I deleted the CodeCatalyst space under the second ID (B) and made sure it was deleted from the associated AWS Account, and also deleted the associated IAM roles and then performed the following steps:
1. In CodeCatalyst space in the original ID (A), it asks me to provide a space name and an AWS account ID for billing. I do this and click the 'Verify in AWS' link, which opens a tab in the AWS Account specified and indicates a Valid Token. When I click on the 'Verify Space' button, it take me to a page titled 'Verify Amazon CodeCatalyst Space' and a message 'Account Verified, you can return to Amazon CodeCatalyst'.
2. Switching back to the CodeCatalyst tab, I now see a message under 'AWS account verification token' saying Approved, and I click on the 'Create Space' button. I do that and I'm taken to the space settings page. Opening CodeCatalyst in the AWS Console, I can also see the space in CodeCatalyst with a status of Connected in the space details, but the Billing details has a current tier of 'None tier'.
3. Back in CodeCatalyst tab, I switch to 'Billing' where it tells me I must add an AWS account for billing. Billing details show as '-' for current tier, AWS account status and AWS account name. Clicking the 'Add an AWS account button', it asks me to choose an AWS account already associated and in the dropdown I choose the account ID I specified, followed by clicking on the 'Change billing account' button. At this point I received a message saying 'An internal error has occurred whilst processing your request' and I click cancel.
4. Switching back to the AWS account tab I navigated to CodeCatalyst in the console, but now I have no Amazon CodeCatalyst spaces. I then switch back to the CodeCatalyst tab and choose the 'Add an AWS account button' again. This time it asks me to add a new account - I enter the account details and an alias and click the 'Associate AWS account' button. I get a message indicating success and too 'Finish setting up by approving the connection with AWS using your connection token xxxx-xxx-xxx-xxxx'.
5. I click on 'Complete Setup in the AWS management console' button which again asks me to verify the Amazon CodeCatalyst space. It opens up the AWS console in CodeCatalyst again and I click the 'Verify Space' button which I do and get the message telling me the account has been verified. However, switching back to the billing tab in CodeCatalyst it still shows no billing details.
6. I've also tried clicking on the 'Manage billing in AWS account' button in CodeCatalyst. This opens the AWS console in CodeCatalyst > Spaces. Opening the space, Billing details shows 'None tier' under current tier, and Allowed tier shows 'Free'. Clicking Edit, allows me to add 'STANDARD' to the allowed billing tiers but there is no way to change the current tier.
7. Switching back to CodeCatalyst shows no changes under under the billing tier, and just asks me to add an AWS account for billing.
At this stage, I delete the space, ensure it has been removed under CodeCatalyst in the AWS console and remove any IAM roles that have been created for CodeCatalyst.
If I now switch back to the second builder ID I created, I am asked to create a space but this time when I'm asked to associate an AWS account, I specify the same AWS account ID and all proceeds normally.
It seems that there is something in the configuration of the first builder ID (the one that originally couldn't create an alias) that prevents a successful association for billing.
asked 16 days ago