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

Set BraveHost Backend in factory function #119

Merged
merged 1 commit into from Aug 4, 2022

Conversation

Szubie
Copy link
Collaborator

@Szubie Szubie commented Aug 3, 2022

A host must always have a Backend due to use for resource checks so this makes sense to enforce in factory function to avoid creation of invalid BraveHosts. Conceptually this aligns with current Bravetools design - there's always a local Backend on the host used for building and deploying.

Update tests and commands to use new function.

BraveHost.HostInfo method now returns info about the bravehost backend - its name implies and fact that it is attached to BraveHost suggests that it should only return information about current host.

…st must always have a Backend (due to use for resource checks) so this makes sense to enforce. Update tests and commands to use new function. Also disallow passing a different backend to BraveHost.HostInfo for now - its name implies and fact that it is attached to BraveHost suggests that it should only return information about current host.
@idroz idroz merged commit f40a602 into bravetools:master Aug 4, 2022
@Szubie Szubie deleted the backend-in-host-func branch August 4, 2022 23:11
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.

None yet

2 participants