-
Notifications
You must be signed in to change notification settings - Fork 43
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
sfdx-hardis v5 #770
Merged
Merged
sfdx-hardis v5 #770
Conversation
This file contains 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
- Internalize packagexml append and removal with local commands, ISO from sfdx-essential ones - sf hardis:packagexml:append - sf hardis:packagexml:remove
nvuillam
force-pushed
the
migrate-sf-plugin
branch
from
September 16, 2024 19:55
ce05196
to
b0fa36b
Compare
Fixes #788
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.
Refactoring explanations
The future deprecation of sfdx force:source:** commands on 6 november finally convinced us to switch everything from SFDX core to SF CLI core. (otherwise existing CI/CD pipelines would not work anymore from this date !)
Therefore, sfdx-hardis required a complete refactoring as described below, but this won't impact existing CI/CD and Monitoring pipelines.
We made many tests but risk zero do not exist, so if you see any bug, please report them ASAP and we'll solve them quickly :)
Major changes
Migrate plugin from SFDX plugin core to SF Cli Plugin core
Change background calls to legacy sfdx commands to call their SF Cli replacements
sfdx force:mdapi:convert
->sf project convert mdapi
sfdx force:mdapi:deploy
->sf project deploy start --metadata-dir
sfdx force:source:retrieve
->sf project retrieve start
sfdx force:source:deploy
->sf project deploy start
sfdx force:source:pull
->sf project retrieve start
sfdx force:source:push
->sf project deploy start
sfdx force:source:tracking:clear
->sf project delete tracking
sfdx force:source:manifest:create
->sf project generate manifest
sfdx sgd:source:delta
->sf sgd:source:delta
sfdx force:org:create
->sf org create sandbox
|sf org create scratch
sfdx force:org:list
->sf org list
sfdx force:org:delete
->sf org delete scratch
sfdx config:get
->sf config get
sfdx config:set
->sf config set
sfdx auth:web:login
->sf org login web
sfdx auth:jwt:grant
->sf org login jwt
sfdx auth:sfdxurl:store
->sf org login sfdx-url
sfdx org:login:device
->sf org login device
sfdx force:data:record:get
->sf data get record
sfdx force:data:record:update
->sf data update record
sfdx force:data:soql:query
->sf data query
sfdx force:data:bulk:delete
->sf data delete bulk
sfdx alias:list
->sf alias list
sfdx alias:set
->sf alias set
sfdx force:apex:test:run
->sf apex run test
sfdx force:apex:execute
->sf apex run
sfdx force:package:create
->sf package create
sfdx force:package:version:create
->sf package version create
sfdx force:package:version:delete
->sf package version delete
sfdx force:package:version:list
->sf package version list
sfdx force:package:version:promote
->sf package version promote
sfdx force:package:installed:list
->sf package installed
sfdx force:package:install
->sf package install
sfdx force:user:password:generate
->sf org generate password
sfdx force:user:permset:assign
->sf org assign permset
sfdx hardis:_
->sf hardis:_
New wrappers commands for SF Cli deployment commands
sf hardis project deploy validate
-> Wrapssf project deploy validate
sf hardis project deploy quick
-> Wrapssf project deploy quick
sf hardis project deploy start
-> Wrapssf project deploy start
New Features / Enhancements
true
, the command will be run only one time per org. A record of SfdxHardisTrace__c is stored to make that possible (it needs to be existing in target org)availableTargetBranches
, using a comma. For examples,- integration,Choose this branch if you are on the BUILD side of the project !
Change Matching Rule
Fixes
Documentation
Deprecations
Deprecate wrapper commands matching sfdx commands that will be removed. All replaced by sf hardis deploy start (TODO: complete !)
sfdx hardis:source:push
sfdx hardis:source:deploy
sfdx hardis:mdapi:retrieve
sfdx hardis:mdapi:deploy
Deprecate
hardis:deploy:sources:metadata
as nobody uses metadata format anymoreRemovals
Replace puppeteer by puppeteer-core: it means that if you use a command requiring puppeteer, please make sure to have a Chrome available in your environment (already integrated within the Docker image)
Get rid of sfdx-essentials plugin dependency by internalizing its used commands
sf hardis:packagexml:append
sf hardis:packagexml:remove
sf hardis:project:clean:filter-xml-content
Remove npm dependencies (some of them not maintained anymore)
Remove not used keyValueStores to keep only Salesforce one
Fixed GitHub issues: