Orchestration migration table missing 'CONFIGURED' 12/105512/1
authorr.bogacki <r.bogacki@samsung.com>
Fri, 3 Apr 2020 10:59:23 +0000 (12:59 +0200)
committerSebastien Premont-Tendland <sebastien.premont@bell.ca>
Wed, 8 Apr 2020 15:32:41 +0000 (11:32 -0400)
Add missing Flyway migration to reduce manual steps for
instantiation use cases.

Issue-ID: SO-2784
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: Ieafafdb9abac3a0b0a4b14d60af5eac1710074c7

adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V9.0__AddConfiguredForVnfOrchestrationStatus.sql [new file with mode: 0644]

diff --git a/adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V9.0__AddConfiguredForVnfOrchestrationStatus.sql b/adapters/mso-catalog-db-adapter/src/main/resources/db/migration/V9.0__AddConfiguredForVnfOrchestrationStatus.sql
new file mode 100644 (file)
index 0000000..81e6092
--- /dev/null
@@ -0,0 +1,2 @@
+INSERT INTO orchestration_status_state_transition_directive(RESOURCE_TYPE, ORCHESTRATION_STATUS, TARGET_ACTION, FLOW_DIRECTIVE)
+VALUES ('VNF', 'CONFIGURED', 'ACTIVATE', 'CONTINUE');