-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: Support bring your own image #942
Conversation
/run pipeline |
1 similar comment
/run pipeline |
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.
variables name should be powervs_ instead of pi for the solution variables. Also validation should be removed here,
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.
Set tf version to >=1.9.0 across all files, upgrade workspace repo version to 2.2.0
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.
- Make changes in catalog.json file to expose the variables to UI. Also think if it makes sense to have 3 fields for custom images on UI ? or just 1 field which supports a dictionary or something and then internally you can convert the dictionary to individual objects.. Make a pre-release and import it to UI to get a feel of it. :)
- Minimum tf version must be >=1.9.0 in all versions.tf file
/run pipeline |
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.
For Quickstart (standard plus VSI) we do not support custom OS image imports. If we do then we should limit it to just one custom image and this image must be given higher priority and used for creating an instance...
We shall discuss on Monday regarding custom image deployment for Quickstart if we need to support it or not.
/run pipeline |
…picks up correctly
/run pipeline |
🎉 This PR is included in version 7.1.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers