deployer | PHP deployment tool with support for popular frameworks | Continuous Deployment library

Have a look at ESLint globals. Basically, you can declare a global value ethers in your ESLint configuration, and that will be treated as defined in all linted files.

For ESLint >= 7, if your configuration file is .eslintrc, add an entry like:

I don't think this is Docker related. Maybe your build process copies files?

"The deployment contains definitions with the same key 'ct-camunda' (id attribute), this is not allowed" Check if you have packaged multiple .bpmn files into your deployment. Maybe you accidentally copied the model file in an additional classpath location. You seem to have two deployments with the same id. (This is not about the filename, but the technical id used inside the XML)

If you are using auto deployment in Spring Boot, you do not have to declare anything in the processes.xml. Use this only in combination with @EnableProcessApplication (or do not use both)

Not possible by design.

A contract address is determined from the deployment transaction params. Specifically, the ethers deploy() function is using the CREATE opcode by default, so the contract address is determined from the deployer address and the deploying transaction nonce param.

But the private key to the contract address is never generated during the deployment - so it can't be returned. Just the address.

Because otherwise I can't call the transfer method on the smart contract.

Correct. If you want to transfer funds out of the contract, you need to implement a function to be able to do that.

The key to your problem was updating PSP.

I would like to add something about PSP:

According to this documentation and this blog:

As of Kubernetes version 1.21, PodSecurityPolicy (beta) is deprecated. The Kubernetes project aims to shut the feature down in version 1.25.

However I haven't found any information in Rancher's case (the documentation is up to date).

Rancher ships with two default Pod Security Policies (PSPs): the restricted and unrestricted policies.

See also:

• The benefits of Pod Security Policy
• Secure Kubernetes cluster PSP
• Pod Security Policies

You are using Java 16 (as shown in the log file) with Maven. In this case, you should use TomEE in version 8.0.9 as this release contains important fixes regarding illegal reflective access (due to the use of Unsafe for proxy creation) in higher versions of Java. You find some details in https://issues.apache.org/jira/browse/TOMEE-3795

It looks like you are using a lower Java version for running your standalone TomEE deployment, which works as it isn't as restrictive as newer Java versions.

Side Note: Java 16 is end-of-life and you should better switch to Java 17.

You can clone the repo and build the image yourself and push it to your container registry. This is one workaround to fix this until the official image is back.

Finally identified the problem: The old maven plugin is deprecated in the new gradle versions.

If you are experiencing this error you need to rewrite your script to use Maven Publish Plugin

You can inherit from other contract. Let's say you want to import from Post contract.

You have a typo in Color.test.js