-
Notifications
You must be signed in to change notification settings - Fork 7
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
Dynamic Imports of SDK Modules #260
Conversation
Issue with linting or unit tests detected. |
No TOKENS are being passed anywhere. I anticipate blackduck scan will be approved once manual review is complete. |
b'## WARNING: A Blackduck scan failure has been waived A prior failure has been upvoted
|
Issue with linting or unit tests detected. |
1 similar comment
Issue with linting or unit tests detected. |
Issue with linting or unit tests detected. |
Issue with linting or unit tests detected. |
Description
Currently we have tagged branches in FCA but those version tags correspond to the Firebolt SDK version and do not have any barring on FCA. There are differences in tagged versions in FCA but they are not required.
This setup causes issues when there is a breaking change that goes into FCA that is also required in every tagged version. These occurrences require a rapid set of PRs to fix all tagged branches and then deploy.
Since the only required difference in the tagged branches is the version of SDK, we can simplify the situation by getting rid of all the tagged branches and just updating the SDK version FCA uses for each build. With each SDK specific FCA build we can deploy to the tagged FCA endpoints.
This PR handles dynamic imports for the FireboltExampleInvoker file as well as the SDK imports in constants.