M
Mark Tarry
When using the Terraform provider, if multiple
port_blueprint
resources are removed in the same
apply
run, the provider will fail with the following error:
Error: failed to delete blueprint
│
│ failed to trigger blueprint deletion with all entities, got:
│ {"ok":false,"error":"other_migration_running_on_blueprint","message":"Other
│ migration is currently running on this
│ blueprint","details":{"otherMigrationId":"mig_9lojp5FqLBAUswnk","blueprintIdentifier":""}}
I've reproduced this when deleting just 2 blueprints - even when neither of those blueprints have entity records.
Re-running the
apply
command seems to get around this. However this instability creates a problem for automated CD workflows.