Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No instructions to add a new or existing simple queue service to recipe schema file #844

Open
aliew opened this issue Jul 11, 2024 · 1 comment
Labels
documentation This is a problem with documentation. p2 This is a standard priority issue queued

Comments

@aliew
Copy link

aliew commented Jul 11, 2024

Describe the issue

Hi guys,

I like to customise my deployment project to be able to create new / use existing simple service queue. I could not find any instructions in the documentation by customizing the recipe file to support this resource. I can only view the one example resource, of adding a Dynamo DB table to the deployment project: https://aws.github.io/aws-dotnet-deploy/tutorials/custom-project/. Are we able to add documentation on what resources are supported with the recipe schema and some examples to accompany this.

Thanks.

Links

https://aws.github.io/aws-dotnet-deploy/tutorials/custom-project/

@aliew aliew added documentation This is a problem with documentation. needs-triage This issue or PR still needs to be triaged. labels Jul 11, 2024
@aliew aliew changed the title No instructions to add a new or existing simple queue service No instructions to add a new or existing simple queue service to recipe schema file Jul 11, 2024
@bhoradc bhoradc added needs-review p2 This is a standard priority issue queued and removed needs-triage This issue or PR still needs to be triaged. needs-review labels Jul 11, 2024
@normj
Copy link
Member

normj commented Jul 23, 2024

The recipe file is used to drive the UI, either VS or the CLI, to guide the user to provide input values into CDK project. With CDK project you can create anything CDK or the AWS SDK support based on the input collected from the UI and passed into the user. The sample you linked to describes how to create UI settings for the name for an existing DDB table or create new. For SQS the process would be basically the same but in the CDK project you would use the CDK constructs for SQS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is a problem with documentation. p2 This is a standard priority issue queued
Projects
None yet
Development

No branches or pull requests

3 participants