DAT-16713 DevOps :: LocalStack for Snowflake Emulation #726
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
…g purposes feat(snowflake.yml): add setup for Python 3.11.5 and configure LocalStack for testing feat(snowflake.yml): install localstack-extension-snowflake and localstack-pro docker image feat(snowflake.yml): wait for LocalStack startup and set environment variables for testing feat(snowflake.yml): update Maven command to use dynamic dbName and dbUrl for testing
…/snowflake.localhost.localstack.cloud" to "jdbc:snowflake://snowflake.localhost.localstack.cloud" to use the correct JDBC connection protocol
jandroav
added
skipReleaseNotes
…kflow feat(snowflake.yml): update liquibase-github-action to version 7 for better compatibility and functionality
feat(snowflake.yml): add environment variable TH_SNOW_URL to store the Snowflake database URL feat(snowflake.yml): update liquibase-github-action step to use environment variables for username, password, and URL chore(snowflake.yml): update Snowflake Test Run step to use environment variables for database admin, username, password, and URL
…re that the localstack-extension-snowflake is installed after starting LocalStack feat(snowflake.yml): add environment variables TH_DB_ADMIN, TH_DB_PASSWD, and TH_DB to the GitHub environment to configure the Snowflake database connection
…e the correct port number (4566) for the Snowflake database connection
…r localstack connection The TH_SNOW_URL value in the snowflake.yml file was updated to include the http protocol for the localstack connection. This change was made to ensure that the connection to the localstack instance is established correctly.
…imeout to avoid potential issues with startup time feat(snowflake.yml): add installation of localstack-extension-snowflake to enable Snowflake support in LocalStack
…ty with the project chore(snowflake.yml): add DEBUG=1 flag to localstack start command for debugging purposes
…ble to the test job to provide the Liquibase Pro license key feat(snowflake.yml): install Liquibase during the test job to enable running Liquibase commands fix(snowflake.yml): update the Status step to use the 'liquibase update' command instead of the liquibase/liquibase-github-action fix(snowflake.yml): remove unnecessary LIQUIBASE_PRO_LICENSE_KEY environment variable from the Snowflake Test Run step
…race logging in LocalStack chore(snowflake.yml): update job name from "Status" to "Update" for clarity
…se-github-action@v7 for better compatibility and maintainability
…ment variable chore(snowflake.yml): update Snowflake Test Run step to use liquibase command instead of maven command for better consistency and simplicity
The Liquibase update step was removed as it is no longer needed for the Snowflake workflow.
…ment variables for URL, username, and password test(snowflake.yml): update Maven command to include new environment variables for database configuration
…bug logging for troubleshooting test failures
…able name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to match secrets configuration fix(snowflake.yml): update LIQUIBASE_PRO_LICENSE_KEY environment variable name to
jandroav
force-pushed
the
DAT-16713
branch
2 times, most recently
from
1463b27
to
48590d9
Compare
…angelog* tables in the script to improve readability and maintainability
…ripts for Snowflake The SQL scripts for adding a column and adding a foreign key constraint were updated to use the correct table and column references. The previous references were using a mix of uppercase and lowercase letters, which caused issues in Snowflake. The updated scripts now use consistent lowercase table and column names, enclosed in double quotes to ensure case sensitivity. This change ensures that the SQL scripts will work correctly in Snowflake.
…lic" schema for consistency and improve readability The table and sequence names in the `createPackage.xml`, `createPackageBody.xml`, `alterSequence.sql`, `createPackage.sql`, `createPackageBody.sql`, `createSequence.sql`, `dropFunction.sql`, `dropSequence.sql`, `renameSequence.sql`, and `valueSequenceNext.sql` files were changed to use the lowercase "public" schema instead of the uppercase "PUBLIC" schema. This change was made to improve consistency and readability in the Liquibase change scripts.
…educe noise in the workflow logs
…t of 30 seconds for LocalStack startup to prevent indefinite waiting period
…at 4:00 AM instead of 6:00 AM 🔧 (aws-weekly.yml): Refactor workflow to include additional database configurations and permissions for different database platforms and versions 🔧 (aws-weekly.yml): Adjust database initialization steps based on the database platform and version selected for testing 🔧 (github actions): Remove unnecessary secrets from the liquibase-github-action configuration. 🔧 (aws-weekly.yml): Update SQL Server suite of tools installation to include sqlengine, sqlclient, and sqlpackage 🔧 (aws-weekly.yml): Add a step to run sqlcmd to create a database named lbcat for MSSQL platform
…meral-cloud-infra.yml instead of DAT-17834 branch
…the workflow to continue even if errors occur ✨ (snowflake.yml): add steps to update diagnose information and archive localstack diagnose for better debugging and monitoring capabilities
… to prevent workflow failure if curl command fails
…ake Test Run jobs to prevent workflow failure on non-critical errors
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.