bcgov / bcgov/entity

TESTING INFRA/PLANNING - How to create valid COBRS coops filings in non-prod envs?

Open
#1,912 0 comments 0 reactions 5 assignees Assigned to @thorwolpert View on GitHub
blocked ENTITY - DO NOT USE
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

In testing #1887, we needed to insert a variety of COBRS coops filings into Oracle in order to watch how the Legal Updater handled them.
The most basic means of doing this was are:
- Borrowing SQL statements from the COLIN API for the filings that exist in the new system
- Using API calls to POST any of the filings that exist in the new system

ISSUE: There isn't a valid means of inserting any of the following new filings that don't exist in the new system yet:
OTRES Restoration Application of a Cobrs Entity
OTSPE Notice of Special Resolution
OTCGM Change of AGM Date and/or Location
OTINC Incorporation Registration Application
OTNCN Change of Name of a Cobrs Entity
OTAMR Amended Annual Report
OTADR Amended Change of Director

Maybe Bob has stored procedures?
Maybe a dev/DBA has another known technique?
Maybe Brian is underway on a solution?

Some discussion is needed to get a strategy going.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.