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.

Sign up for GitHub

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

Jump to bottom

channel_block module doesn't need an operation field #272

Closed
sstone1 opened this issue Jun 4, 2020 · 0 comments
Closed

channel_block module doesn't need an operation field #272

sstone1 opened this issue Jun 4, 2020 · 0 comments
Assignees
@sstone1
Labels
enhancement New feature or request

Comments

@sstone1
Copy link
Contributor

sstone1 commented Jun 4, 2020

No description provided.

@sstone1 sstone1 added the enhancement New feature or request label Jun 4, 2020
@sstone1 sstone1 self-assigned this Jun 4, 2020
sstone1 pushed a commit to sstone1/ansible-collection that referenced this issue Mar 25, 2021
Remove operation parameter from channel_block module (resolves IBM-Bl…
432e2fa 
…ockchain#272)

The `operation` parameter in the `channel_block` module only has one option, `fetch`.

Remove the `operation` parameter from this module and make it like any other Ansible
module by having a `state` parameter instead. When `state` is set to `present`, ensure
that the block is fetched from the specified channel and stored at `path`. When `state`
is set to `absent`, ensure that there is no block stored at `path`.

These changes are compatible because any existing `operation` parameters will be ignored,
and the `state` parameter defaults to `present`, preserving existing behaviour.

Signed-off-by: Simon Stone <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sstone1 sstone1

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sstone1