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

action :delete & action :destroy #186

Closed
matiasdecarli opened this issue Oct 2, 2014 · 4 comments
Closed

action :delete & action :destroy #186

matiasdecarli opened this issue Oct 2, 2014 · 4 comments
Assignees
Labels
Type: Bug Doesn't work as expected.
Milestone

Comments

@matiasdecarli
Copy link

Reading the docs, I can see that "delete" is a option for the machine resource

screen shot 2014-10-02 at 4 23 59 pm

But when I use it

  Chef::Exceptions::ValidationFailed
  ----------------------------------
  Option action must be equal to one of: nothing, allocate, ready, setup, converge, converge_only, destroy, stop!  You passed :delete.

  Cookbook Trace:
  ---------------
    /home/vagrant/cookbooks/matiasdecarli/recipes/create_container.rb:55:in `block in from_file'
    /home/vagrant/cookbooks/matiasdecarli/recipes/create_container.rb:52:in `from_file'

  Relevant File Content:
  ----------------------
  /home/vagrant/cookbooks/matiasdecarli/recipes/create_container.rb:

   50:  
   51:  machine "deploy-to-delete" do
   52>>   action :delete
   53:  end
   54: 

Am I doing something wrong here? I can use destroy, but this doesnt delete the node, only the container. Thanks in advance

@johnewart johnewart added this to the 1.0 milestone Oct 10, 2014
@johnewart johnewart added the bug label Oct 10, 2014
@johnewart
Copy link
Contributor

Apparently we don't have delete as a supported action in the metal machine resource... I'll tag this as a bug for 1.0; should be an easy fix.

@jkeiser
Copy link
Contributor

jkeiser commented Nov 6, 2014

This should be a doc fix.

@esciara
Copy link

esciara commented Dec 26, 2014

Hi there. Came across this problem and it does not feel safe that the doc does actually not reflect the really. Looks like this a fairly widespread problem. I feel it has been quite some effort to figure out how things work, and absence/wrongness of doc has not helped.

Trying to put a constructive spin to this: is there any way that the doc could be generated from the code, just to make sure it is up to date?

@jkeiser
Copy link
Contributor

jkeiser commented Feb 27, 2015

This is fixed. https://docs.chef.io/resource_machine.html#actions

As for autogenerating docs, it's definitely on a list. Will take some sphinxing though. @jamescott and I have talked about it, but we haven't got to it yet.

@jkeiser jkeiser closed this as completed Feb 27, 2015
@tas50 tas50 added Type: Bug Doesn't work as expected. and removed Bug labels Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Doesn't work as expected.
Development

No branches or pull requests

5 participants