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!

Allow the secret() resource in chef-client v17 to use non-default authentication paths

Ref support ticket #30273

The issue is that when authenticating with approles, we don’t use the default path (/auth/customapprolespath/login). There is no built in mechanism to specify the approle mount_point, so our token fetch fails every time. Can the secret() resource be updated with a config option to accept a different authorization path (eg /auth/#{mypath}/login) instead of forcing the default?

  • Guest
  • Mar 25 2022
  • New
  • Attach files
  • Guest commented
    25 Mar 03:08pm

    This request is specifically related to Hashicorp's vault.