FAQs for Continuous Delivery

Why are Lite plan services deleted after 30 days of inactivity?

An instance of Continuous Delivery is considered active when one or more of the toolchains within the same resource group is active. A toolchain is considered active if users interact with it by way of the UI, delivery pipeline jobs are triggered, or repositories that are managed by Git Repos and Issue Tracking are accessed.

When these conditions aren't met for all toolchains that are associated with the Continuous Delivery service for 30 days, the instance is considered inactive.

Can I use sample scripts to build and deploy my application?

The open-toolchain/commons GitHub repo contains a collection of common scripts that you can use in toolchains and pipelines. For example, you can use one of the shell scripts that is contained in this repo within your own toolchains in various ways.

How do I bring my own code and deploy it by using Continuous Delivery?

You can choose any of the following options to deploy your own code to Continuous Delivery:

• Create a toolchain by using one of the available templates (dependent on the deployment target and tool integrations). On the Create a Toolchain page, select the appropriate provider for your source repository, and then specify the link to your source code repo. After you create your toolchain, you might need to adjust the pipeline scripts for your deployment goals.
• Create an empty toolchain, and then add tool integrations to deploy your app. For more information about using this method to deploy your code to Continuous Delivery, see Deploy an app on Kubernetes.

How do I find the status of IBM Cloud and the Continuous Delivery service?

Check the IBM Cloud Status page to determine whether known issues are affecting the IBM Cloud platform and the major services in IBM Cloud.

You can find the Status page by choosing either of the following options:

• In the IBM Cloud console, go to Support. From the Today's notifications widget, click View all, and then click Status to view the status of resources in all IBM Cloud locations. You can view a list of events, in chronological order, for maintenance and incidents. You can search across all notifications, or filter by type, geographic locations, and individual resources. You can also view planned maintenance windows for which prior notice is provided and unplanned incidents or outages, which are posted as soon as the IBM Cloud team becomes aware of them. Incident notifications are regularly updated until they're resolved.
• Access it directly at IBM Cloud - System Status.

For more information about the IBM Cloud Status page, see Viewing IBM Cloud status.

How do I remove authorized users from the Continuous Delivery service?

You can remove authorized users from the Continuous Delivery service and prevent them from being added again.

• Remove the user's access in IAM to all toolchains in the resource group.
• Remove the user from the authorized user list in the Continuous Delivery service instance.
• Remove Developer access from all Git Repos and Issue Tracking repos that are attached to all of the toolchains in the resource group.

You can maintain an activity log related to authorized users. For more information about viewing, managing, and auditing service-initiated and user-initiated activities in your IBM Cloud® Continuous Delivery instances, see IBM Cloud Activity Tracker Event Routing events. For more information about managing authorized users, see Authorized users.

Why is the AUTHORIZED_USERS_PER_MONTH quantity reported in IBM Cloud Billing and usage different from the actual number of authorized users listed for my Continuous Delivery service instance?

The AUTHORIZED_USERS_PER_MONTH quantity is computed as an average of the number of authorized users per day. If authorized users are added or removed, the average will increase or decrease. For example, if a service instance has one authorized user for the first half of June, then a second authorized user is added on June 16, the AUTHORIZED_USERS_PER_MONTH quantity for the entire month of June will be 1.5.

Why is the AUTHORIZED_USERS_PER_MONTH quantity reported in IBM Cloud Billing and usage equal to zero for my Continuous Delivery service instance?

The service instance resides in an account in an enterprise, and is participating in consolidated billing. When consolidated billing is enabled on a Continuous Delivery service instance in an enterprise account, only that instance will report a non-zero quantity of authorized users. All other Continuous Delivery service instances in the enterprise hierarchy and in the same region will report zero authorized users, even though they continue to list their authorized users. For more information about consolidated billing, see Consolidated billing.

Can I avoid being billed for the same authorized users in multiple instances of the Continuous Delivery service?

If your Continuous Delivery service instances are organized into an enterprise, you can enable consolidated billing on a Continuous Delivery service instance in the enterprise account so that authorized users are only reported for billing once for all service instances within the enterprise and in the same region. For more information about consolidated billing, see Consolidated billing.

Can I manage Continuous Delivery service instances by using Terraform?

You can use Terraform to provision, update, and de-provision instances of the Continuous Delivery service. For more information about using Terraform with Continuous Delivery, see Creating a Continuous Delivery service instance with Terraform, Deleting a Continuous Delivery service instance with Terraform, and the ibm_resource_instance resource documentation.

You cannot use Terraform to manage the list of authorized users for a Continuous Delivery service instance. You can manage the list of authorized users only by using the console. For information about authorized user management, see Authorized users.

Can I manage Continuous Delivery service instances by using an API?

You can use HTTP APIs or selected programming language SDKs to provision, update, and de-provision instances of the Continuous Delivery service. For more information about using Continuous Delivery with the API, see Creating a Continuous Delivery service instance with the API and Deleting a Continuous Delivery service instance with the API.

You cannot use APIs to manage the list of authorized users of a Continuous Delivery service instance. You can manage the list of authorized users only by using the console. For information about authorized user management, see Authorized users.

Can I use the console, APIs, or CLI to modify resources that are managed by Terraform?

When you use Terraform to manage resources such as Continuous Delivery service instances, toolchains, and Tekton pipelines, avoid changing the resources by using the console, APIs, or CLI, or by any other method outside of Terraform's control.

If you circumvent Terraform by directly changing resources, you might cause resource drift, a situation in which the states of your actual resources on IBM Cloud deviate from the definition of the resources in Terraform. The next time that you apply the Terraform configuration, Terraform attempts to update your resources to bring them back in alignment with the Terraform configuration. This action might lead to unintended consequences, such as reverting changes or deleting and then re-creating resources.

For more information about resource drift, see Manage Resource Drift.