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

Assigns Viridian as the default coordinator for cloud invocations [API-1556] #145

Merged
merged 4 commits into from
Sep 28, 2022

Conversation

utku-caglayan
Copy link
Contributor

No description provided.

@utku-caglayan utku-caglayan added this to the v5.2.0 milestone Sep 26, 2022
@netlify
Copy link

netlify bot commented Sep 26, 2022

Deploy Preview for eclectic-sawine-19fcf1 canceled.

Name Link
🔨 Latest commit e51609e
🔍 Latest deploy log https://app.netlify.com/sites/eclectic-sawine-19fcf1/deploys/6333e4590fc3a20008b35bc6

run.go Outdated
return err
}

func setDefaultCoordinator(logger *log.Logger) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why does this function get a logger as parameter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It logs if it can not assign the default URL. Do you suggest an alternative flow?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe you can just return the error. Since if the coordinator URL cannot be set we shouldn't continue to run the command anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think for many usecases this may be non-critical. For those cases just logging makes sense for me. Wdyt?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it's a serious problem if the user intends to connect to Viridan but it can't since the coordinator URL was not set correctly. What we can do is to call setDefaultCoordinator only when we know the user wants to connect to the cloud.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good idea, updated as discussed e51609e

@yuce
Copy link
Collaborator

yuce commented Sep 26, 2022

@utku-caglayan Could you also change:

--cloud-token string    your Hazelcast Cloud token

to:

--cloud-token string    your Hazelcast Viridian token

run.go Outdated Show resolved Hide resolved
run.go Outdated Show resolved Hide resolved
Copy link
Collaborator

@yuce yuce left a comment

Choose a reason for hiding this comment

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

Looks good!

@utku-caglayan utku-caglayan merged commit df1e3d6 into hazelcast:main Sep 28, 2022
@degerhz degerhz modified the milestones: v5.2.0, v5.2.0-beta3 Oct 31, 2022
@yuce yuce removed this from the v5.2.0-beta3 milestone Dec 9, 2022
@degerhz degerhz added this to the v5.2.0-beta3 milestone Mar 22, 2023
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

3 participants