Nick Mancuso

It would be great to allow some configuration like: ```xml END_OF_TERM ``` Example of desired behavior: Given we have a subscription, S, and a subscription plan, P. In both scenarios,...

@sbrossie can you point me to where the proration logic is handled?

We were able to utilize the `org.killbill.subscription.align.effectiveDateForExistingSubscriptions` property discovered at https://docs.killbill.io/latest/userguide_configuration#_subscription_properties to achieve the `END_OF_TERM ` behavior described above at https://github.com/killbill/killbill/issues/2079#issuecomment-2591466228.

Hi pierre, Thanks for the quick reply, and the debugging tips. From a quick glance at the code, I thought that kpm somehow used maven to download the artifact, which...

Here is what the maven-metadata.xml looks like: ```xml com.company hello-world-plugin 2.0.1 2.0.1-SNAPSHOT 2.0.1 20240422151152 ```

>Or I'm guessing this would be for https://maven.pkg.github.com:443/company/hello-world-plugin/com/company/hello-world-plugin/2.0.1-SNAPSHOT/hello-world-plugin-2.0.1-20240422.151152-1.jar.sha1 Yes, sorry, bad copy/paste/obfuscation on my part. >Is your company able to provide a patch? I would love to, however I do...

We have worked around this issue by defining the following environment variable in our deployment: ``` env: - name: KILLBILL_QUEUE_CREATOR_NAME valueFrom: fieldRef: fieldPath: metadata.name ``` ``` ➜ ~ curl -s...

If this approach is generally acceptable I will clean this up, add some logging, and additional checks.

Hm, over time this is creating a large number of fields: ``` tomcat@killbill-78f9c49cbf-4fbpm:~$ jmap -histo 1024 | head Picked up JAVA_TOOL_OPTIONS: -Xms4G -Xmx14G num #instances #bytes class name (module) -------------------------------------------------------...