fix: [ASSMT-476]: include Spinnaker credentialsInfo in the payload #126
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.
When migrating Spinnaker pipelines into Harness, there are Spinnaker stages that uses accounts in Spinnaker but the configuration of the stage does not have the cloudProvider type behind the accountName.
To handle those cases, we are sending information about the credentials in Spinnaker in the payload to be able to determinate the cloudProvider type and migrate to the correct cloud provider.
The payload now looks like the following: