DBDAART-9052-find/fix-hardcoded-schema-names#119
Open
alihashmi-wh wants to merge 1 commit into
Open
Conversation
per discussion on the ticket, https://jiraent.cms.gov/browse/DBDAART-9052, submitting this change to one file to parameterize the schema reference found here
Contributor
|
Hi @alihashmi-wh I see some file paths in the same program that have taf-python in them, do you think we need to update those as well? |
Contributor
|
@alihashmi-wh can this PR be closed? |
This file contains hidden or 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
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.
What is this and why are we doing it?
per discussion on the ticket, https://jiraent.cms.gov/browse/DBDAART-9052, submitting this change to one file to parameterize the schema reference found here
What are the security implications from this change?
none
How did I test this?
no formal testing - given limited permissions to execute code in databricks
Should there be new or updated documentation for this change? (Be specific.)
n/a
PR Checklist