Cloud Services

Enterprise Marketplace

Provisioning policies
Published On Oct 07, 2024 - 11:30 AM

Provisioning policies

Update the visibility for a catalog based on team or context.
Servicification support allows you to set up policies for Catalog Provisioning to prevent users from accessing catalogs they are not allowed to. You can do this by team, by context, or a combination of the two. For example, you might want to limit European users to storage devices located in Europe. This technique that can only be used for these data types:
  • Array:
    • Multiselect
  • String:
    • selectOne
    • searchList
    • radio

Change visibility of a catalog

You can set a catalog to not be visible, and therefore unable to be ordered by, certain individuals in your organization. This can be done by team, context, or a combination of the two. To change the visibility for a catalog, complete the following steps:
  1. On the
    Catalog Management
     page, click
    Add Services
    . To learn more about navigating to the different services from each tenant, refer to Landing page navigation or Kyndryl Bridge Landing page navigation.
  2. Click the
    Actions
     icon next to the catalog you want to change and select
    View Details
    .
  3. Click the
    Configuration Parameters
     tab.
  4. Click the
    Actions
     icon for the parameter you want to adjust and select
    View Details
    .
  5. Click
    Edit
    .
  6. In the
    Values
     section, click
    Add Context Combination
    .
  7. In the
    Add Context Combination
     window, select any combination of context and team.
  8. In the
    Make Available to Parameter Values
     section, select the values that you want available to that combination.
  9. Click
    Save
    .

Reordering configuration groups, sections, and attributes

The configuration groups, sections, and attributes are displayed in the order that they are listed on this tab. You can change them as needed with the
Reorder
 feature.
For example, if you want to group all your load balancer configuration attributes, create a new Load Balancer configuration group and move the attributes into it.
If you have any visibility rules, the dependent sections and attributes must always be listed after the attributes that they are dependent on.
If you want to change this order, complete the following steps:
  1. Navigate to the
    Configuration Parameters
     tab.
  2. Click
    Reorder
     in the upper right.
  3. Click and drag the items as desired.
  4. Click
    Save
     in the upper right.
Reorder is not currently supported for sections and configuration groups.

Previewing catalogs

The Service Designer can preview a catalog to verify/validate how the order configuration options will be presented to the Buyer, based on their customizations. You will be shown the form as it would be viewed by the buyer and can fill it out to test its features without provisioning the catalog. Because there is no validation or on-the-fly preview while you are editing, you can only validate your changes using the
Preview
 option. To preview a catalog, complete the following steps:
  1. Navigate to the
    Catalog Management
     page. To learn more about navigating to the different services from each tenant, refer to Landing page navigation or Kyndryl Bridge Landing page navigation.
  2. Click the
    Actions
     icon for a catalog in the Draft or Work in Progress state and select
    Preview
    .
You can also preview a catalog by clicking
Preview
 in the upper right of the
Details
 page for the catalog. To get to the
Details
 page, click the
Actions
 icon for the catalog and selecting
View Details
.

Known limitations

The following are the known limitations with the catalog management feature:

General limitations

The following limitations are common across all providers:
  • The sequence is mismatched between the
    Configuration Parameters
     page and the
    Preview
     page. When an attribute is added after a section, that attribute is displayed above the section. However, during the preview it is displaying after the section (which is expected).
  • All newly added sections are displayed below as they are grouped together.
  • An empty section is not visible during the preview.
  • Users are not able to delete multiple catalogs from the Draft section.
  • Multiple catalogs cannot be retired simultaneously by selecting multiple check boxes (feature is not implemented yet).
  • User is not able to unretire multiple catalogs (feature is not implemented yet).
  • User cannot delete multiple catalogs from the Retired state (feature is not implemented yet).
  • A new import job will not start if a previous job is still in progress.
  • When
    Import from File
     is performed after
    Import from Provider Account
    , the history displays the name of the provider account for the catalog that was imported from file.
  • If an exported file is imported multiple times, the import only gets passed the first time. All subsequent attempts fail. Versioning is not supported so it is considered as a duplicate entry.
  • If the user exports any catalog from a server/tenant and tries to import it again on the same tenant, it fails because the catalog ID must be unique for every catalog on a particular tenant. If you want to onboard the same exported content on the same tenant/server, add a unique catalog ID in all the required places in the exported content.
  • Users are unable to re-import servicified content that has been deleted.
  • If some catalogs have been selected in the
    Draft
     tab and the user navigates to another tab, catalogs in the same index from the list get auto selected on all tabs.
  • After entering valid credentials (GitHub token) and selecting
    TestConnection
    , the user gets an "Invalid Credentials" error message.
  • If you try to import a zip that contains files from multiple providers (such as Azure and Alibaba), then discovery gets completed for the Alibaba files and fails for the Azure files.
  • While adding a new attribute, if the user adds a validation on an attribute, then the default value is not validated against the same validation rule.
  • The UI does not display multiple error messages returned by the APIs. Only the first error message is shown on the UI.
  • The
    Search
     field on the
    Configuration Parameters
     page is not functional.
  • The
    Static Value
    ,
    Derived Value
    , and
    Derived from External Source
     fields are not properly hidden for some
    Data Type
     and
    Input Type
     combinations.
  • Validations are not added for the
    Required
    ,
    Selected
    ,
    Editable
    , and
    Configurable
     fields.
  • The “Edit Success” message is displayed even if the user clicks
    Edit
     but saves without making any changes.
  • When editing catalog details, there is no placeholder to edit the heading for each feature or add multiple descriptions.
  • Adding fixed sections is not currently supported.
  • While creating a new configuration group, the
    Call to Validate
     does not currently work.
  • The section sequence on Configuration Parameters is as follows:
    • Configurations within a configuration group are always displayed at the top of the group.
    • A section within a configuration group is always displayed at the bottom of the group.
  • Reorder is working only for Attributes and not for Groups/Sections.
  • Empty sections are not visible on the
    Additional Parameters
     page when the user previews the catalog.
  • When users import an empty .zip file, the catalog does not send valid zip content to integration and the job gets failed.
  • Users can add multiple hide expressions for the same config (all providers except for Amazon Web Service).
  • A section/attribute name created with special characters like @#!%&... cannot be deleted.
  • A user can disable the
    Required
     property for configs that are discovered after servicification while editing the configuration attribute.
  • While editing catalog details, there is no placeholder to edit the heading for each feature or add multiple descriptions to one feature.
  • While adding a section there is no placeholder on the UI for
    fixedSectionItems
    .
  • A catalog cannot be published with empty configuration groups or sections.
  • A removable property for Section is applicable only for the EDIT catalog flow.
  • For existing tenants, user will have to explicitly set the
    discoverContent
     and
    manageSOEnabled
     flags to
    true
    .
  • Even if the array
    'icbCatalogRepository'
     in
    icb_catalog_metadata.json
     file has multiple objects defined for a particular provider with different sourcepaths added in it, it will discover the content from only one sourcePath.
  • If there are a lot of configuration groups, sections, and attributes for the catalog and the scrollbar is enabled on the page, re-order is not possible from the top of the page to the bottom.
  • The user cannot add multiple hide expressions for same configuration feature at this moment. If a second hide expression is added, then it will either overwrite the previous one (GCP and Alibaba) or generate an error message (all other providers).

Alibaba Cloud

The following limitations are specific to Alibaba Cloud:
  • The
    Derived Value
     feature is not yet supported.
  • The
    Import Failed Count
     field in the job status email always shows the count as 0 even if failures occurred during the job.
  • If you provide an empty section in the template, then that empty section will not be visible during preview.

Amazon Web Services

The following limitations are specific to Amazon Web Services:
  • Data Type: String-Download and Input Type: Downloadable are not provided by the UI.
  • There is no
    Description
     field in the
    Service Details
     page so users cannot add a description for the onboarded native template.
  • The "Configure Region" config group is displayed at second position on the
    Configuration Parameter
     page. Ideally it should be on top for all the catalogs.
  • Parsing of an AWS native YAML template (with short syntax form intrinsic functions) is technically not possible in
    nodejs
     for
    cb-aws-catalog-int
    . The
    library'cfn-flip'
     is the only Python library that can support AWS native YAML template conversion that is already supported in CLI-based servicification.
  • Even if the array
    'icbCatalogRepository'
     in the
    icb_catalog_metadata.json
     file will have multiple objects defined for the AWS provider with different sourcePaths, it will only discover the content from one sourcePath.
  • The catalog does not support a user-defined
    sourcePath:"somezipfile.zip"
     file, so integration does not receive valid zip content and the job fails. However, if users define
    sourcePath:"/"
    and place the .zip file containing native templates in this directory, then servicification is successful.
  • The
    Import Failed Count
     field in the job status email always shows the count as 0 even if failures occurred during the job.
  • If the user edits a configuration attribute by changing the
    Values
     option from
    Derived Value
     to
    Static Value
     without providing any values for the
    Static Value
     option, then any
    Derived Value
     metadata that was saved earlier will be retained.

Google Cloud Provider

The following limitations are specific to Google Cloud Provider:
  • The
    Derived value
     feature is not yet supported.
  • Nested
    .zip
     file structures are not supported.
  • The UI allows exporting catalogs in WIP format, but this format is not supported from the integrations side. Therefore, the user will get a success message after exporting the WIP catalog, but the catalog will not be available in the zip file.

IBM Cloud

The following limitations are specific to IBM Cloud:
  • Cancel discovery from the
    Catalog Admin
     page is not yet implemented for IBM Cloud
  • A pricing error is displayed if a user reorders the template's default configs into a new section.
  • Users cannot add
    Derived From External Source
     metadata without specifying a parent configID.
  • The
    Derived value
     feature is not yet supported.
  • If there are multiple Terraform files for a catalog, all files should be in a folder. Importing a
    .zip
     file containing more than one Terraform file for same catalog (
    main.tf
    ,
    variables.tf
    ,
    provider.tf
     ) at sourcePath without being in a folder will not work.

Microsoft Azure

The following limitation is specific to Microsoft Azure:
  • If the source path of exported content has multiple compressed files, only the first
    .zip
     file will be considered for import.
Do you have two minutes for a quick survey?
Take Survey