Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
Documentation that gives the minimal set of instructions required to work with Proton. Preferably here.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
I'm trying to understand how to use Proton, but I'm struggling to hold all the information required to interact with it in my mind long enough to create a working PoC.
The documentation I've found on AWS usually involves a lot of text, even on the getting started sections, and links to templates that are full featured involving a lot of bells and whistles. I think the objective of those pieces of documentation are striving to show how to use the full feature set of Proton in a way that allows it to be used effectively in production.
I would have liked to have started with a simple step by step process to create the minimal resources required to interact with Proton without forking any templates or anything. I think this would help me understand what is the minimum I'd need to set up in order to work with Proton before worrying about the extra features I can leverage.
I think instructions on going from git init to a provisioned S3 bucket or something would give me a much better footing than I currently have in Proton, and might help others that are new to the service.
Are you currently working around this issue?
How are you currently solving this problem?
Gonna try to read through the docs again.
Additional context
Anything else we should know?
We're a Terraform shop, and the instructions here involve provisioning roles and buckets with CloudFormation to support usage of Terraform. I think a lot of organizations like ours that use Terraform already have solutions for managing Terraform state and would prefer to provision the relevant IAM role using Terraform. The well documented support for selecting an existing bucket and an IAM policy would be preferable to provisioning those resources through CloudFormation.
Community Note
Tell us about your request What do you want us to build?
Documentation that gives the minimal set of instructions required to work with Proton. Preferably here.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
I'm trying to understand how to use Proton, but I'm struggling to hold all the information required to interact with it in my mind long enough to create a working PoC.
The documentation I've found on AWS usually involves a lot of text, even on the getting started sections, and links to templates that are full featured involving a lot of bells and whistles. I think the objective of those pieces of documentation are striving to show how to use the full feature set of Proton in a way that allows it to be used effectively in production.
I would have liked to have started with a simple step by step process to create the minimal resources required to interact with Proton without forking any templates or anything. I think this would help me understand what is the minimum I'd need to set up in order to work with Proton before worrying about the extra features I can leverage.
I think instructions on going from
git initto a provisioned S3 bucket or something would give me a much better footing than I currently have in Proton, and might help others that are new to the service.Are you currently working around this issue? How are you currently solving this problem?
Gonna try to read through the docs again.
Additional context Anything else we should know?
We're a Terraform shop, and the instructions here involve provisioning roles and buckets with CloudFormation to support usage of Terraform. I think a lot of organizations like ours that use Terraform already have solutions for managing Terraform state and would prefer to provision the relevant IAM role using Terraform. The well documented support for selecting an existing bucket and an IAM policy would be preferable to provisioning those resources through CloudFormation.