Skip to content
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

Added Always First Functionality #173

Open
wants to merge 20 commits into
base: master
Choose a base branch
from

Conversation

CaptCorpMURICA
Copy link

@CaptCorpMURICA CaptCorpMURICA commented Apr 26, 2023

This pull request resolves #164.

  • This enables the new file type F__*.sql which is processed before all other file types.
  • This option defaults to False but can be enabled with the configuration -af or --always-first. This ensures that these files can be selectively executed depending on the environment.
    • e.g. In the CI/CD pipeline, you enable this configuration option when you need to clone the production environment to create the QA environment. However, this option is turned off for the elevation from QA to Prod because no cloning operation is taking place.
  • Tests were added to ensure the functionality works as designed. These tests cove:
    • Returning the proper number of files executed when the option is turned on or off.
    • Returning expected errors based on naming conventions.
    • Validating the appropriate data for the Change History Table.
  • Added this new functionality to the README documentation.

CaptCorpMURICA and others added 18 commits April 25, 2023 15:37
Added tests to ensure always first files are executed properly including: executing multiple files, executing no files when option is False, expected error handling, and file execution order.
Added the ability to execute specific files first in the execution order as well as an option to turn off processing of these files altogether. This functionality is best used when rebuilding the QA or STG clones during the CI/CD process.
Added documentation around Always First functionality from Issue 164
Added Always First parameter to tests
Duplicate apply_change_script was identified in the Always First processing block. It was not needed and removed.
@CaptCorpMURICA
Copy link
Author

Is there an update on when this will be reviewed?

@sfc-gh-tmathew sfc-gh-tmathew added enhancement New feature or request Development in Progress Will be addressed in upcoming release labels Nov 2, 2023
@sfc-gh-tmathew
Copy link
Collaborator

@CaptCorpMURICA Will discuss this next week and get back to you. Thank you for your contribution and your patience while we catchup on open items and PRs.

@jzking
Copy link

jzking commented Jan 17, 2024

Any discussion on when this might make it into a release? Thank you

@CaptCorpMURICA
Copy link
Author

Any discussion on when this might make it into a release? Thank you

I just welcomed my first child, so I haven't had the ability to implement the requested changes. I'll try to get it wrapped up in the next month or so.

@jzking
Copy link

jzking commented Jan 17, 2024

Any discussion on when this might make it into a release? Thank you

I just welcomed my first child, so I haven't had the ability to implement the requested changes. I'll try to get it wrapped up in the next month or so.

Congratulations !! Let me know if I can help (with this PR, you are on your own with the baby LOL!)

@mw243270
Copy link

Any update on this one?

@rvanlinge-scripps
Copy link

It'd be great to add into the README file along with the other prefix file name section

@hawle
Copy link

hawle commented Nov 6, 2024

Can we bump this? I would need this functionality in production already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development in Progress Will be addressed in upcoming release enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Always Execute First Functionality Option to change order of execution for scripts
6 participants