fix deploy for dmo package#110
Open
zach-maddox wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Packages for DMO transforms cause an exception to be thrown when the CLI is used to deploy the code package into Data Cloud. This change enables those packages to be deployed successfully without the exception.
Note: at the time of submitting this PR, there is still a bug where if the output DMO does not exist, the transform creation will fail, yielding a different error (but the code package still uploads successfully). This is a bug inside Data Cloud that is being addressed, with the end result being that the output DMO should be created automatically. The workaround is to create the DMO some other way (via Transform builder UI or Transform API) before creating a transform with the code package.