Skip to content
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

feat!: new provider.yaml and new contracts v2 [JS-850, JS-851] #1082

Merged
merged 62 commits into from
Jan 8, 2025

Conversation

shamsartem
Copy link
Collaborator

No description provided.

@shamsartem shamsartem changed the title feat: new provider.yaml feat: new provider.yaml [JS-850] Dec 24, 2024
Copy link

linear bot commented Dec 24, 2024

@shamsartem shamsartem changed the title feat: new provider.yaml [JS-850] feat: new provider.yaml and new contracts [JS-850] Dec 26, 2024
@shamsartem shamsartem changed the title feat: new provider.yaml and new contracts [JS-850] feat: new provider.yaml and new contracts [JS-850, JS-851] Dec 26, 2024
Copy link

linear bot commented Dec 26, 2024

JS-851 Use contracts v2

@shamsartem shamsartem changed the title feat: new provider.yaml and new contracts [JS-850, JS-851] feat: new provider.yaml and new contracts v2 [JS-850, JS-851] Dec 26, 2024
@shamsartem shamsartem changed the title feat: new provider.yaml and new contracts v2 [JS-850, JS-851] feat!: new provider.yaml and new contracts v2 [JS-850, JS-851] Jan 7, 2025
const [invalidPeers, peers] = splitErrorsAndResults(
computePeers,
({ kubeconfigPath, ipSupplies, name, ...restPeer }) => {
return kubeconfigPath === undefined || ipSupplies.length === 0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need that?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not anymore cause now all of this is required in the config instead of being optional

@shamsartem
Copy link
Collaborator Author

Merging to enable testing. Will refactor and improve later, feel free to leave code-review comments

@shamsartem shamsartem merged commit 3894079 into main Jan 8, 2025
9 checks passed
@shamsartem shamsartem deleted the new-provider-config branch January 8, 2025 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants