Feature #15674

Implement host disassociation command

Added by Lukas Zapletal about 4 years ago. Updated almost 2 years ago.

Target version:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:


We are missing this bit completely from CLI.

From our mailing list:

Anyone know of a command line option in hammer to disassociate a host from
its compute resource? It's easily done through the GUI however I am
attempting to do this as a part of a larger workflow built in something
like Ansible and need to be able to disassociate via CLI.

Related issues

Related to Hammer CLI - Bug #13596: hammer: unable to remove association between hostgroup and environmentClosed

Associated revisions

Revision 3c5d3944 (diff)
Added by Shira Maximov almost 2 years ago

Fixes #15674 - add disassociate command to host


#1 Updated by Martin Bacovsky about 4 years ago

  • Related to Bug #13596: hammer: unable to remove association between hostgroup and environment added

#2 Updated by Dominic Cleal about 4 years ago

Compute resource disassociation is different to the case in #13596. Environments are a single attribute on a host/host group and it should be possible to set them to null, while compute resource disassociation is performed by a specific action (PUT /api/v2/hosts/:id/disassociate).

#3 Updated by Bryan Kearney about 4 years ago

  • Bugzilla link set to 1356126

#4 Updated by Tomáš Strachota about 2 years ago

  • Category changed from Foreman commands (obsolete) to Hosts

#5 Updated by Shira Maximov about 2 years ago

  • Triaged set to No
  • Assignee set to Shira Maximov

#6 Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request added

#7 Updated by Anonymous almost 2 years ago

  • Status changed from Ready For Testing to Closed

#8 Updated by Tomer Brisker almost 2 years ago

  • Fixed in Releases hammer-cli-foreman-0.14.0 added

Also available in: Atom PDF