Configure and perform life-cycle operations on discovered resources

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 2 min. de leitura

    • Configure life-cycle operations on cloud resources that are not provisioned using ServiceNow® Cloud Provisioning and Governance. Provision resources and modify resource block operations to perform day-2 operations on cloud resources that are discovered using Cloud Discovery but not provisioned using Cloud Provisioning and Governance.

    Antes de Iniciar

    • Assign the configuration item (CI) to a user who performs the operation.
    • Role required: sn_cmp.cloud_service_user, root_admin, admin, or sn_cmp.cloud_admin

    Por Que e Quando Desempenhar Esta Tarefa

    If a resource is provisioned from the Cloud Provisioning and Governance catalog, you can perform base system life-cycle operations on a stack or on a resource. However, if a resource is discovered as part of Cloud Discovery and is not provisioned from Cloud Provisioning and Governance, the same Start/Stop, Deprovision operations are not available, by default. The following procedure is applicable for a Stop operation on a virtual machine that is not provisioned from Cloud Provisioning and Governance.

    Procedimento

    1. Navigate to All > Cloud Admin Portal > Design > Resource Blocks.
    2. Search and open the resource/CI you want to perform life-cycle operations on.
    3. Set toggle switch to Draft, to make the resource block editable.
    4. In the selected Resource Block > Operations tab, select the required Interface and Operation from their respective lists.
      Nota:
      The Interface and Operations fields are only available for resources that are discovered but not added or generated to catalog.
    5. Click the Override Operation icon.
    6. In the Override Operation dialog, specify a name for the Interface-operation.
      The Create New check box is selected, by default.
    7. Click Submit.
      You have enabled the selected operation for the interface you created.
    8. In the Input Parameters form, click the Add Input Parameters icon.
    9. Specify resourceID as the parameter Name and click Save.
      By default, a system assigned expression is generated and appears in the Mapping field.
    10. For the ServerID parameter, replace the default expression in the Mapping field with ${parameter.resourceId} and click Save.
    11. Navigate to Operations > Steps subtab.
    12. In the Input form, change the NodeId parameter value to ${parameter.resourceId}.
    13. Navigate back to the Input Parameters form, and click Generate Catalog.
    14. Set toggle switch to Published, to publish the resource block again.
      You have configured the resource operation for the specific resource/CI.
    15. Opcional: Navigate to Cloud User Portal > Resources > Virtual Machine Instance, and select the virtual machine instance for which you created the resource operation.
    16. Opcional: Select the new interface operation you created from the Select Resource Operations list.

    O que Fazer Depois

    Navigate to the Cloud User Portal > Resources > Virtual Machine Instance and select the new interface operation you created from the Select Resource Operations list.