-
Notifications
You must be signed in to change notification settings - Fork 390
feat(vm): Add blueprint metadata for compute_instance module #539
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
base: main
Are you sure you want to change the base?
Conversation
bharathkkb
left a comment
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.
Lets not check in the lock file
bharathkkb
left a comment
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.
@q2w can you take a look for metdata?
| sourceType: git | ||
| dir: /modules/compute_instance | ||
| version: 13.6.1 | ||
| version: 13.6.3 |
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.
why are we changing this version here?
| - name: instances_details | ||
| description: List of all details for compute instances | ||
| type: | ||
| - tuple |
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.
should this be list instead of tuple? Same comment for other places where tuple is being used
| enable_vtpm: bool | ||
| source_instance_template: string | ||
| tags: | ||
| - set |
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.
should this be list instead of set? Same comment for other places where set is used
No description provided.