-
Notifications
You must be signed in to change notification settings - Fork 13
docs: update README #521
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
docs: update README #521
Conversation
|
/run pipeline |
|
/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.
see my feebdack
README.md
Outdated
| > module.ocp_base.data.ibm_container_vpc_worker_pool.all_pools["default"] | ||
| > module.ocp_base.data.ibm_container_vpc_worker_pool.all_pools["secondarypool"] | ||
| > module.ocp_base.ibm_container_vpc_worker_pool.pool["default"] | ||
| > module.ocp_base.ibm_container_vpc_worker_pool.pool["secondarypool"] |
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.
@Aashiq-J I think your saying that we only need to run the state remove command on the default worker pool right? So to avoid any confusion, can you make that clear? Perhaps update the grep to only return default pool in its output?
README.md
Outdated
| $ terraform state rm "module.ocp_base.ibm_container_vpc_worker_pool.pool[\"default\"]" | ||
| ``` | ||
|
|
||
| Schematics Example: For a cluster with 2 worker pools, named 'default' and 'secondarypool', follow these steps: |
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.
Do we even need to mention 'secondarypool' here? Regardless of how many other pools there are or what they are called, your always going to run the state remove command on the default pool right?
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
|
/run pipeline |
|
🎉 This PR is included in version 3.30.2 🎉 The release is available on GitHub release 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