srvr | a little http server | REST library

You need to add an escape character in front of the $. In the case of PowerShell, the escape character is `

This is usually found on the top left hand side of your keyboard, next to the number 1. Its called the "backtick".

For Example:

$Value = "sqlcmd -E -S `$(ESCAPE_SQUOTE(SRVR))"

or in your case

It said, it lacks git_url, and username.

You cannot set the Process scope permanently, it is only valid for the current process (source):

The Process scope only affects the current PowerShell session. The execution policy is saved in the environment variable $env:PSExecutionPolicyPreference, rather than the registry. When the PowerShell session is closed, the variable and value are deleted.

If a scope is Undefined, it will inherit its policy from a higher level scope:

The effective execution policy is determined by the order of precedence as follows:

• MachinePolicy. Set by a Group Policy for all users of the computer.
• UserPolicy. Set by a Group Policy for the current user of the computer.
• Process. Affects only the current PowerShell session.
• CurrentUser. Affects only the current user.
• LocalMachine. Default scope that affects all users of the computer.

In your case, Process will inherit from CurrentUser and CurrentUser will inherit from LocalMachine. Therefore, Bypass will be effective for the Process scope.

You can verify your current, effective execution policy by executing Get-ExecutionPolicy with no parameters.

This is actually directly possible with update_page(), though you are correct, it is not documented in the method's documentation.

I found in the source code that the method update_page() takes an optional argument version_comment. This is the comment that you want to set.

Extending your example:

After a week I came up with the below configuration that worked,

As per comments under the question,
this was a bug, which has been reported by OP and fixed in the development branch.

Make sure you are using the java.net.preferIPv4Stack property on the server side as well.

Check your firewall config, to make sure that all listed ports are open.

The issue is w/the communication SPI which, by default is using 47100 and up port range see: https://ignite.apache.org/docs/latest/clustering/network-configuration#communication

You're trying to set two mismatching cache configurations with the same name. Have a look at this message:

I figured what the issue is here. Apparently it has to do with the way I configured the service object in kubernetes. I am not sure if this is a bug or a feature but it looks like an Ignite node can only scale to node and not across nodes. What I mean by this is the service object should be unique to a node. If you share the service object across nodes (microservices) expecting the cluster to spread across multiple nodes it will hang. (I am not sure if this is an anti-pattern) What worked was keeping the service object unique to the node and then scaling the node if required.

I think if this is the case then we should probably keep the ignite nodes as a separate cluster and not embedded within the micro-services.