Customer request: Clarify the content of the order emails as they are not aligned with the bill and we cannot use them as audits (i.e. they display $0.00 as unit price)
Invoice enhancement: Improve clarity to charging mechanism
Customer request: Improve clarity to the charging mechanism, i.e. to indicate which are monthly items being billed in advance and which are usage-based which are billed in arrears, and clearly show the period of time which every item refers to.
Group the items logically to provide clarity in what services are displayed as separate items in the invoice (currently, these include New services and Cloud Object Storage)
Invoice enhancement: Changes during billing period
Customer request: If Item changes during billing period make clear how much was consumed before and after the change, and any extra charges applied for the change operation
Change Kubernetes worker node machine type in place
This is derived from a GitHub issue for the IBM Cloud terraform provider. The request there is to make it possible to change the machine type of the worker nodes of a Kubernetes cluster.
It is not possible to change the machine type via terraform ...
Request to display the list of tags or the "given name" of the resource (hostname, name of load balancer, name of object storage bucket, etc.). There is a need for multiple tagging use cases, but the top priority is for billing information.
SHA-256 is the "padlock" mechanism inside cryptocurrencies like Bitcoin, and while it does the job for now, its based on a generating engine that has some faults, namely different inputs giving the same outputs technically called collisions. The S...