Skip to content
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

ibm_pi_image docs should link to the catalog images ibm_pi_catalog_images #5047

Closed
powellquiring opened this issue Jan 16, 2024 · 0 comments · Fixed by #5571
Closed

ibm_pi_image docs should link to the catalog images ibm_pi_catalog_images #5047

powellquiring opened this issue Jan 16, 2024 · 0 comments · Fixed by #5571
Assignees
Labels
documentation service/Power Systems Issues related to Power Systems

Comments

@powellquiring
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

New or Affected Resource(s) or Datasource(s)

  • ibm_pi_image

Description

References

https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/pi_image#pi_image_storage_pool

image

The catalog is one place the id can come from. Not sure if there is another place? Make this clear on this doc page. Here is another place to fix up:

image

See #5044 (comment) this would help as well.

  • #0000
@github-actions github-actions bot added the service/Power Systems Issues related to Power Systems label Jan 16, 2024
@michaelkad michaelkad self-assigned this Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation service/Power Systems Issues related to Power Systems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants