This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help us process your pull request efficiently, please include:
(Required) Short description of changes in the PR topic line
Added optional flag --mem-allocated to vdc.py and updated vdc help to include fully qualified options for create
(Required) Detailed description of changes include tests and
documentation. If the pull request contains multiple commits with
detailed messages, refer to those instead
1 Added Optional Tag for --mem-allocated
2. Added additional detailed help for vcd vdc with options for AllocationPool
3. Added @click.option for '--mem-allocated' with description
4. Added mem_allocated to dev create.
Tested against - VMware Cloud Director version: 10.1.2.16779297
Purpose for change :
In trying to add a vdc with --allocation-model AllocationPool had the following error
Status code: 400/BAD_REQUEST, [] The value for allocated memory must be above zero. You provided 0.