grunt-sf-tooling
Advanced tools
Grunt tasks to retrieve and updated SalesForce components via the Tooling API
Grunt tasks to retrieve and update SalesForce components via the Tooling API.
This plugin requires Grunt ~0.4.5
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-sf-tooling --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-sf-tooling');
In your project's Gruntfile, add a section named sfpush to the data object passed into grunt.initConfig(). This task lets you update components in SalesForce.
grunt.initConfig({
sf_password: 'Example Password',
sf_username: 'example@example.com',
sfpush: {
options: {
// Task-specific options go here.
classes: ['ExampleApexClass']
},
sandbox: {
options: {
// Organization specific options
loginServer: 'test.salesforce.com',
username: 'example@example.com.example'
}
},
},
});
Type: String
Default value: '30.0'
A string value that sets the SalesForce api version used.
Type: Array
Default value: []
An array that holds a list of Apex Classes to be saved.
Type: String
Default value: 'SF Grunt Container'
A string value that is used as the Name of the MetadataContainer when saving SalesForce components.
Type: String
Default value: 'login.salesforce.com'
A string value that sets the server used to log into SalesForce.
Type: Array
Default value: []
An array that holds a list of Apex Pages to be saved.
Type: String
Default value: null
A string value that sets the password used to log into SalesForce. It can be set globally with the sf_password attribute.
Type: Array
Default value: []
An array that holds a list of triggers to be saved.
Type: String
Default value: null
A string value that sets the username used to log into SalesForce. It can be set globally with the sf_username attribute.
Type: Boolean
Default value: false
A boolean value that is used to control if SalesForce components are only validated and not saved.
Type: String
Default value: './components/'
A string value that sets the path where SalesForce components are located.
under construction
In your project's Gruntfile, add a section named sfpull to the data object passed into grunt.initConfig(). This task lets you download components from SalesForce.
grunt.initConfig({
sf_password: 'Example Password',
sf_username: 'example@example.com',
sfpull: {
options: {
// Task-specific options go here.
classes: ['ExampleApexClass']
},
sandbox: {
options: {
// Organization specific options
loginServer: 'test.salesforce.com',
username: 'example@example.com.example'
}
},
},
});
Type: String
Default value: '30.0'
A string value that sets the SalesForce api version used.
Type: Array
Default value: []
A array that holds a list of Apex Classes to be pulled with the sf_pull task.
Type: String
Default value: 'SF Grunt Container'
A string value that is used as the Name of the MetadataContainer when saving SalesForce components.
Type: String
Default value: 'login.salesforce.com'
A string value that sets the server used to log into SalesForce.
Type: Array
Default value: []
An array that holds a list of Apex Pages to be downloaded.
Type: String
Default value: null
A string value that sets the password used to log into SalesForce. It can be set globally with the sf_password attribute.
Type: Array
Default value: []
An array that holds a list of Apex Triggers to be downloaded.
Type: String
Default value: null
A string value that sets the username used to log into SalesForce. It can be set globally with the sf_username attribute.
Type: String
Default value: './components/'
A string value that sets the path where SalesForce components are located.
under construction
FAQs
Grunt tasks to retrieve and updated SalesForce components via the Tooling API
The npm package grunt-sf-tooling receives a total of 0 weekly downloads. As such, grunt-sf-tooling popularity was classified as not popular.
We found that grunt-sf-tooling demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.