amigoscode / cohort-2-c Goto Github PK

• liquibase table
• entity
• repository
• service
• controller
• DTO

• set up terraform cloud project and workspace as source for IaC-state of AWS Organization master account.
• set up workspace' execution mode "local"
• set up Vault on Master Local Machine
• create AWS Organization
• create Sandbox, PROD and STAGING accounts as DEV OrangizationUnit
• review default SCP settings with regard of using SSO

• liquibase table
• entity
• repository
• service
• controller
• DTO

• liquibase table
• entity
• repository
• service
• controller
• DTO

• create shared Workspace
• create shared variables
• implement simple automate API tests with JS
• add API tests to CI\CD-pipelines

• liquibase table
• entity
• repository
• service
• controller
• DTO

add global custom error exception
add custom error response

• liquibase table
• entity
• repository
• service
• controller
• DTO

• create SSO Identity Store
• set up permission sets
• set up permission groups
• set up policies
• set related attachemnets
• invite team members

• liquibase table
• entity
• repository
• service
• controller
• DTO

• liquibase table
• entity
• repository
• service
• controller
• DTO

• liquibase table
• entity
• repository
• service
• controller
• DTO

• add required dependencies

• add abstract audit class

• setup liquibase

• liquibase table
• entity
• repository
• service
• controller
• DTO

I suggest reconsidering original implementation of Git-Flow for the sake of Gitlab-Flow because this will prevent us from being overwhelmed by branching hell and on the flip side it'll give us an opportunity to have and deploy 2 environments.

Gitlab Flow

• main is our dev-branch
• all features and bugfixes (except for hotfixes which we won't face soon) are to be pushed into MAIN
• main branch is ought to have STAGING branch;
• staging branch is ought to have PROD branch;
• all the changes merely flow downstream, so it makes sure that all changes are tested in all environments;
• upstream-principle: should we find a bug in one of the environments, we'll create a feature-branch of main and cherry-pick changes to all environments.

Or, maybe we could make use of Github-flow with only main branch, where changes are deployed sequentially into different environments.

• liquibase table
• entity
• repository
• service
• controller
• DTO