Advanced

The Bitbucket integration supports additional flags to provide additional configuration, making it easier to configure its behavior to your liking.

Using advanced configurations

The following advanced configuration parameters are available:

Spec path

The specPath parameter specifies a string that Port's Bitbucket app will use when constructing search paths leading to a yml file, every path in the repository which ends with the specPath value will be scanned.

• Default value: port.yml
• Use case:
  • If you want the app to scan a different file than port.yml (for example, change configure the app to scan files named my-port-config.yml using the pattern my-port-config.yml);
  • If you want the app to ignore port.yml files in certain paths.

Delete dependent entities

The deleteDependentEntities parameter is used to enable deletion of dependent Port entities. This is useful when you have two blueprints with a required relation, and the target entity in the relation should be deleted. In this scenario, the delete operation will fail if this flag is set to false if the flag is set to true, the source entity will be deleted as well.

• Default: false (disabled)
• Use case: Deletion of dependent Port entities. Must be enabled, if you want to delete a target entity (and its source entities) in a required relation.

Enable merge entity

The enableMergeEntity parameter specifies whether to use the create/update or create/override strategy when creating entities listed in a port.yml file.

• Default value: true (use create/update)
• Use case: use false if you want Bitbucket to be the source-of-truth for catalog entities. Use true if you want to use Bitbucket as the source for some properties of entities in the catalog, and use other sources to for properties which are subject to change automatically.

All of the advanced configurations listed below can be added to the port-app-config.yml file.