-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAT-17834 Ephemeral AWS infra for liquibase-test-harness #819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…flow for testing Cloud Databases with test-harness using Terraform Action 🔧 (aws-weekly.yml): Configure workflow to run every Sunday at 6:00 AM and allow manual triggers with specified test classes and databases to start up 🚀 (aws-weekly.yml): Implement jobs for setup, deploying ephemeral cloud infrastructure, initializing MySQL databases, and running tests on various database platforms and versions ✨ Add support for running tests on different database platforms and versions using Maven 🔧 Update test run configurations to include database platform, version, username, password, and URL 🔧 Add support for running tests on AWS Aurora database platform 🔧 Include logic to archive test results for AWS RDS databases 🔧 Implement logic to destroy ephemeral cloud infrastructure after testing phase
…at 4:00 AM instead of 6:00 AM 🔧 (aws-weekly.yml): Refactor workflow to include support for various database types in the test execution process
…workflow configuration.
…ostgresql:aurora' and include 'postgresql' for deployment decision-making. Remove unnecessary whitespace at the end of the file.
…ck for 'postgresql' database type and exclude 'postgresql:aurora' from the check
…ove security and access control in the workflow job.
…configuration to improve readability and maintainability
…abase connections to include correct resource id suffix 🔧 (aws-weekly.yml): Remove unnecessary secret-ids for other database connections to streamline the workflow and improve readability
…sed on the matrix version (aws or aurora) to improve flexibility and security in accessing database credentials.
….yml workflow to use the master branch instead of a specific branch for consistency and stability. Also, adjust the conditions for the aws_postgresql variable to include versions 12, 13, and 14 for better compatibility.
…o DAT-17834 for both deploy and destroy jobs to align with the changes made in the referenced file.
…s based on database platform and version selected during setup. Adjust database cleanup and initialization steps accordingly for MySQL databases on AWS and Aurora.
… to access outputs for databasePlatform and databaseVersion to ensure correct conditional execution based on dependencies. 🔧 (aws-weekly.yml): Update references to 'steps.setup.outputs' to 'needs.setup.outputs' to correctly access outputs from previous job steps.
…f 'needs' for accessing outputs from previous steps. This ensures correct data retrieval for database platform and version configurations. ⬆️ (aws-weekly.yml): Update references from 'needs.setup.outputs' to 'steps.setup.outputs' to align with workflow changes and improve consistency.
…al-cloud-infra before test job for proper execution order
…amline workflow and improve efficiency 🔧 (aws-weekly.yml): Simplify database initialization steps for different database platforms to enhance maintainability and readability
…rsions instead of individual conditions for 'aws' and 'aurora' versions
…" suffix for cloud databases to differentiate from regular databases 🔧 (aws-weekly.yml): update liquibase url to use TH_AURORA_MYSQLURL for aurora database version 🔧 (aws-weekly.yml): add new mysql_cloud.sql file with initial SQL scripts for cloud database tables "authors" and "posts"
…s only for MySQL databases when the version is 'aws' or 'aurora'
…e before executing SQL commands for better clarity and consistency
…ABLE IF EXISTS syntax to improve script readability and maintainability
…r 'aws' and 'aurora' versions to streamline workflow and avoid unnecessary configurations.
…AWS and Aurora versions using Liquibase
…for mysql due to mysql driver issue on GitHub actions.
…MySQL databases and unnecessary comment to streamline workflow and improve readability.
…n consistency in the workflow file 📝 (mssql.sql): Add database creation and switching commands for better database management and setup
… configuration for sqlcmd execution
… resource ID for MSSQL host configuration
… with comma for sqlcmd connection 🔧 (mssql.sql): remove explicit USE [lbcat] statement as the database is now created dynamically during workflow execution
…ariable transformation and echo statements
Label error: This PR is being prevented from merging because you have not added one of the labels: breakingChanges, newContributors, notableChanges, sdou, skipReleaseNotes, TypeBug, TypeEnhancement, TypeTest. You'll need to add it before this PR can be merged. |
…day at 4:00 AM instead of 6:00 AM 🔧 (aws-weekly.yml): Update the version of the ephemeral-cloud-infra.yml workflow to DAT-17834 🔧 (aws-weekly.yml): Add support for different database types in the deploy-ephemeral-cloud-infra job 🔧 (aws-weekly.yml): Add permissions for contents read and id-token write in the init-mysql job 🔧 (aws-weekly.yml): Add configuration for different database types in the init-mysql job 🔧 (aws-weekly.yml): Add configuration for different database types in the test job 🔧 (aws-weekly.yml): Add permissions for contents read and id-token write in the test job 🔧 (aws-weekly.yml): Update the configuration to get AWS secrets based on database platform and version in the test job 🔧 (aws-weekly.yml): Update GitHub Action to install a SQL Server suite of tools and run sqlcmd for MSSQL platform 🔧 (aws-weekly.yml): Add conditional logic to destroy ephemeral cloud infrastructure based on specified databases in inputs
…ral-cloud-infra.yml instead of DAT-17834 branch. Remove trailing whitespace.
…lity and maintainability.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.