Skip to content

Conversation

mdumandag
Copy link
Contributor

We are now defaulting to the Viridian, instead of Cloud, so that our documentation should also reflect that.

Therefore, I have replaced usages of Hazelcast Cloud with Hazelcast Viridian in this PR.

We are now defaulting to the Viridian, instead of Cloud, so that our
documentation should also reflect that.

Therefore, I have replaced usages of Hazelcast Cloud with
Hazelcast Viridian in this PR.
- Client Runtime Stats
- Client Operating Systems Stats
- Hazelcast Cloud Discovery
- Hazelcast Viridian Discovery
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we use this term in Java client docs? @Serdaro Should we update them as well? FYI

_logger.warning("Failed to load addresses from Hazelcast Viridian: %s", e)


class HazelcastCloudDiscovery:
Copy link
Contributor

Choose a reason for hiding this comment

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

What about the name of the class?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can't change that, as it is sometimes used in the wild for monkey patching the coordinator URL. We would break people's code. The same goes for the configuration element cloud_discovery_token

@mdumandag mdumandag merged commit f8a2dc9 into hazelcast:master Mar 28, 2023
@mdumandag mdumandag deleted the cloud-to-viridian branch March 28, 2023 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants