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

add support for specifying volume metadata #48081

Merged
merged 1 commit into from
Apr 4, 2019
Merged

add support for specifying volume metadata #48081

merged 1 commit into from
Apr 4, 2019

Conversation

gtema
Copy link
Contributor

@gtema gtema commented Nov 5, 2018

add possibility to specify metadata (properties) to be set on the volume

SUMMARY

In some cases it is required to specify metadata for the volume. With this PR this is added

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

module/cloud/openstack/os_volume

ANSIBLE VERSION
ansible 2.7.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/gtema/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.7.1 (default, Oct 23 2018, 18:19:07) [GCC 8.2.1 20180801 (Red Hat 8.2.1-2)]
ADDITIONAL INFORMATION

a new module parameter (dict) metadata is being added

@gtema
add support for specifying volume metadata
6ee1a1e 
add possibility to specify metadata (properties) to be set on the volume
@ansibot
Copy link
Contributor

ansibot commented Nov 5, 2018

Hi @gtema, thank you for submitting this pull-request!

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Nov 5, 2018

cc @cloudnull @dagnello @emonty @evrardjp @juliakreger @mnaser @odyssey4me @rcarrillocruz @Shrews
click here for bot help

@ansibot ansibot added affects_2.8 This issue/PR affects Ansible v2.8 cloud community_review In order to be merged, this PR must follow the community review workflow. feature This issue/PR relates to a feature request. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. openstack python3 support:community This issue/PR relates to code supported by the Ansible community. labels Nov 5, 2018
@bcoca bcoca removed needs_triage Needs a first human triage before being processed. labels Nov 5, 2018
@mnaser
Copy link
Contributor

mnaser commented Nov 5, 2018

shipit

@ansibot ansibot added the stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. label Nov 13, 2018
@gtema
Copy link
Contributor Author

gtema commented Apr 4, 2019

-stale_ci

@gtema
Copy link
Contributor Author

gtema commented Apr 4, 2019

recheck

@ansibot ansibot added owner_pr This PR is made by the module's maintainer. shipit This PR is ready to be merged by Core automerge This PR was automatically merged by ansibot. and removed community_review In order to be merged, this PR must follow the community review workflow. stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. labels Apr 4, 2019
@ansibot ansibot merged commit d0745ed into ansible:devel Apr 4, 2019
@gtema gtema deleted the volume_metadata branch April 5, 2019 06:47
@gtema gtema mentioned this pull request Apr 5, 2019
Closed
@ansible ansible locked and limited conversation to collaborators Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
affects_2.8 This issue/PR affects Ansible v2.8 automerge This PR was automatically merged by ansibot. cloud feature This issue/PR relates to a feature request. module This issue/PR relates to a module. openstack owner_pr This PR is made by the module's maintainer. python3 shipit This PR is ready to be merged by Core support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@gtema @ansibot @mnaser @bcoca