-
Notifications
You must be signed in to change notification settings - Fork 63
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
Additional CLI option to identify deploy file #758
Comments
+100 for this |
Hello, thanks for the suggestion @Extend-Apps. We'll keep this in mind when adding new enhancements in the future and if more users request it. |
+1 This would allow deployment of high level customizations (i.e. span multiple deployment objects) without the overhead of creating and managing entirely separate SDF projects. |
It would be a good enhancement. We had to run our own automation to replace the deploy.xml file dynamically when deploying |
This is becoming such a problem now. NetSuite SDN asks us to create/deploy a SuiteApp in the same TSDRV ... and to create any distributed objects like secrets, and integration records in the same TSTDRV account. Yet, if we try and deploy to that TSTDRV with those object files .. the deployment fails. So, developers end up deleting the object files from the project ... they mistakenly commit the deletion to the repo ... and around and around we go. I can't see this being a big lift? Something has to be done here. |
Hi @Extend-Apps, I understand the pain here. This has to be addressed in the netsuite SDF first. Could you file an issue in netsuite about this and ask to assign it to SDF (SuiteCloud Development Framework)? |
Select the SuiteCloud tool where you encountered the issue
SuiteCloud CLI
Version of the SuiteCloud Tool
1.8.0
Operating system
macOS Ventura 13.5.2
Node Version / VSCode Version
v20.5.1
JAVA Version
java 17.0.5+9-LTS-191
Bug description
NOT A BUG
A Feature Request to provide the CLI an option (--deploy ) to allow a user to specify which deploy.xml file to use during deployment.
This would allow a developer to create different deploy.xml files to expand/contract the files/objects to be deployed
Steps To Reproduce
suitecloud project:deploy --deploy deploy_withTests.xml
Actual Output
No response
Expected Output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: