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.
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
Add/keypair #8
base: master
Are you sure you want to change the base?
Add/keypair #8
Changes from all commits
95222fd
b8c4fc8
d025518
fe49844
b6d006c
fba0011
feb1e3e
7edc94a
31dc315
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of optional, I understand that both keys doesn't have to be provided if
use_existing_resource: False
, and are mandatory ifuse_existing_resource: True
.Is that right? If so, please modify the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
use_existing_resource
is inherited from the template you provided at the begining. I was reading about it and I think is anOpenStack-plugin
(and othe plugins) feature, but nothing I had implemented. I think it is not working and we can remove this property all along the plugin.The plugin generates the keypair if
public_key
orprivate_key
is not defined. As I explained before,use_existing_resource
is not taked into account.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then remove
use_existing_resource
, because it seems that it is implemented.Also, the generation of the keys if they are not defined should be reflected somehow in the README.
simulate property is implemented?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, simulate is implemented. If it's
True
it does nothing during the operationThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I said, this should always be defined in the dictionary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think to provide a default user could help to simplify the plugin user experience by means of the blueprints
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is very unlikely that, if you left the username empty, the user in the image will be 'user'. So leaving it blank would lead to an error.
The idea is that, when you define an image, you need to know the default user that the image defines.
Therefore it should be mandatory (and reflect that on the README), unless you say that the plugin is creating the user when deploying the virtual machine. If it is the second case, that behaviour should be explained in the README as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the second assumption is the right case. The user is created during contextualization