You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Description
Currently we are using restapi_object for creating ICR plan and quota so it would be better if terraform provider has the support to create ICR plan and quota. The problem with using the restapi is that if we modify the storage quota or traffic pull limit, we cannot revert back to the previous values as restapi does not store the previous configurations.
New or Affected Resource(s)
ibm_cr_plan
ibm_cr_storage_quota
ibm_cr_traffic_quota
Potential Terraform Configuration
resource"ibm_cr_plan""plan" {
plan="standard"
}
resource"ibm_cr_storage_quota""container_registry_storage_quota" {
storage_megabytes=500
}
resource"ibm_cr_traffic_quota""container_registry_traffic_quota" {
traffic_megabytes=5120
}
# These all resource block should either take registry as an input or read the corresponding registry from the provider.
References
#0000
The text was updated successfully, but these errors were encountered:
Community Note
Description
Currently we are using
restapi_object
for creating ICR plan and quota so it would be better if terraform provider has the support to create ICR plan and quota. The problem with using the restapi is that if we modify the storage quota or traffic pull limit, we cannot revert back to the previous values as restapi does not store the previous configurations.New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: