Chef Ideas
We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
Ah, I think I got confused about session token versus sts:assumerole. Yeah, I don't personally have a need for that, but seems reasonable others might.
Attachments Open full size
we do via api, just not in ui:https://github.com/chef/automate/blob/master/components/compliance-service/docs/adding_test_data.md#adding-cloud-integrations
Attachments Open full size
I mean, both ideally, I just didn't think we had temp cred support for non-govcloud yet to even consider it an option!
Attachments Open full size
will users only need access key/secret support? or will we also need to test/support the session token (temp cred) connection?
Attachments Open full size