Add Option to Disable Creation of Default Resources in Hosted Integrations
L
Luc Verhoeven
We recently deployed a SonarQube integration using the hosted solution. Due to our custom IaC setup, we use non-standard blueprint names, but the integration continues to install blueprints and pages with default names.
I attempted to disable this using the initializePortResources: false option in the configuration, but it had no effect. It would be helpful to have an option to completely disable the creation of default resources.
M
Mark Tarry
We've had the same (frustrating) experience with the Port hosted Jira integration.
We want to ingest specific sets of Jira tickets into custom blueprints, but the 4 default blueprints keep:
- being recreated in our data model
- adding new pages to our catalogue - which are accessible to all usersby default, and will never contain any entities
I've resorted to revoking "view" access to the unwanted catalogue pages for now, but we should be able to prevent these blueprints from being created (and re-created!) in the first instance.
M
Mark DeBeer
We have experienced the same issue with the Port hosted LaunchDarkly integration. We decided to use custom blueprints and deleted the supplied blueprints but they keep returning. This causes confusion with some users because they may not be able to tell the difference between the blueprints at first glance.