The PIFSC Centralized Authorization System (CAS) Containerized Oracle Developer Environment (CCODE) project was developed to provide a custom containerized Oracle development environment (CODE) for the CAS. This repository can be forked to extend the existing functionality to any data systems that depend on the CAS for both development and testing purposes.
-
- URL: https://github.com/noaa-pifsc/PIFSC-CAS-Containerized-Oracle-Development-Environment
- Version: 1.2 (git tag: CAS_CODE_v1.2)
- Upstream repository:
- DSC CODE (DCODE) Version Control Information:
- URL: https://github.com/noaa-pifsc/PIFSC-DSC-Containerized-Oracle-Development-Environment
- Version: 1.2 (git tag: DSC_CODE_v1.2)
- DSC CODE (DCODE) Version Control Information:
* Note: all dependencies are implemented as git submodules in the modules folder
-
- folder path: modules/AAM
- Version Control Information:
- URL: https://picgitlab.nmfs.local/centralized-data-tools/authorization-application-module
- Database: 1.2 (Git tag: central_auth_app_db_v1.2)
-
- folder path: modules/DSC
- Version Control Information:
- URL: <[email protected]:centralized-data-tools/pifsc-dsc.git>
- Database: 1.1 (Git tag: dsc_db_v1.1)
-
- folder path: modules/CDS
- Version Control Information:
- URL: <[email protected]:noaa-pifsc/PIFSC-Container-Deployment-Scripts.git>
- Scripts: 1.1 (Git tag: pifsc_container_deployment_scripts_v1.1)
- See the CODE Prerequisites for details
- See the CODE Repository Fork Diagram for details
- See the CODE Runtime Scenarios for details
-
- Recursively clone the CCODE repository to a working directory
-
- See the CODE Build and Run the Containers for details
-
- create_docker_schemas.sql is executed by the SYS schema to create the DSC schema and grant the necessary privileges
- deploy_dev_container.sql is executed with the DSC schema to deploy the objects to the DSC schema
-
- create_docker_schemas.sql is executed to create the CAS schemas, roles, and APEX workspace
- deploy_dev_container.sql is executed with the CAS schema to deploy the objects to the CAS schema
- deploy_apex_dev_container.sql is executed with the CAS_APX_APP schema to deploy the objects to the CAS_APX_APP schema and the app to the CAS_APX_APP APEX workspace
-
- *Note: this process will fork the CCODE parent repository and repurpose it as a project-specific CODE
- Fork this repository
- See the CODE Implementation for details
-
- See the CODE Upstream Updates for details
- See the CODE container architecture documentation for details
-
- docker/.env was updated to define an appropriate APP_SCHEMA_NAME valu and to specify an TARGET_APEX_VERSION to re-enable Apex
- custom_deployment_functions.sh was updated to add the CODE-ords.yml configuration file to enable the ords container
- custom-docker-compose.yml was updated to define CODE-specific mounted volume overrides for the database and application deployments
- custom_db_app_deploy.sh was updated to deploy the CAS database schemas and the Apex app
- custom_container_config.sh was updated to define DB credentials and mounted volume file paths for the CAS SQL scripts
- See the CODE connection information documentation for details
-
- Connection information can be found in create_docker_schemas.sql
-
- Connection information can be found in create_docker_schemas.sql
See the LICENSE.md for details
This repository is a scientific product and is not official communication of the National Oceanic and Atmospheric Administration, or the United States Department of Commerce. All NOAA GitHub project code is provided on an ‘as is’ basis and the user assumes responsibility for its use. Any claims against the Department of Commerce or Department of Commerce bureaus stemming from the use of this GitHub project will be governed by all applicable Federal law. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by the Department of Commerce. The Department of Commerce seal and logo, or the seal and logo of a DOC bureau, shall not be used in any manner to imply endorsement of any commercial product or activity by DOC or the United States Government.