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!
Our team is bootstrapping short lived azure scale set instances to chef that after few minutes/hours are deleted and removed via chef's API. However, those nodes are still lingering in automate for several dates based on our data lifecycle policy and there is no way to clean them up without effecting other node types. To the point where there are ~30 live nodes in chef but over 2k still visible in automate.
So the idea would be to either:
1) Expose new chef automate's API endpoint that would allow us to remove the bootstrapped nodes completely from its database
2) Add a new parameter to chef's API endpoint and knife node/client delete commands that would also remove them from automate's database