Add a one billing period free trial

[smarlowucf]

This will run a empty metering on the first bill and archive the usage records. After the first billing period the adapter will begin billing usage as normal.

[rtamalin]

LGTM

[smarlowucf]

This is hard coded to one billing period but could be easily extended to allow for a configurable trial period length.

[rtamalin]

This is hard coded to one billing period but could be easily extended to allow for a configurable trial period length.

Yeah I noticed that. Would just have to have a means for passing in the value for the initialisation of the cache settings to pick it up...

Of course if the cache ever gets deleted and then recreated, it would result in an additional trial period, right?

[smarlowucf]

Of course if the cache ever gets deleted and then recreated, it would result in an additional trial period, right?

Yes. It would be the same issue even if the trial period were calculated from the adapter start date though. Since the start date is stored in the cache. It would get reset as well.

[smarlowucf]

Updated base to staging branch.

[rjschwei]

I think we can add a second check on the length of the billing record history.

if cache.get('trial_remaining', 0) and len(get_metering_archive()) > 1:
   liar_liar_pants_on_fire()

where liar_liar_pants_on_fire, with a nicer name of course, propagates some message to the UI. We already have the UI propagation facility in place if I recall correctly.

[smarlowucf]

I think we can add a second check on the length of the billing record history.

if cache.get('trial_remaining', 0) and len(get_metering_archive()) > 1:
   liar_liar_pants_on_fire()

where liar_liar_pants_on_fire, with a nicer name of course, propagates some message to the UI. We already have the UI propagation facility in place if I recall correctly.

It would work as it is now with a trial period of 1. However, if the period was configurable we'd need another value trial_period_length to calculate archive > trial_period_length. For now it's fine though.

Do we want to mark the adapter status as "not compliant"? or only post a warning message?

[rjschwei]

I think we can add a second check on the length of the billing record history.

if cache.get('trial_remaining', 0) and len(get_metering_archive()) > 1:
   liar_liar_pants_on_fire()

where liar_liar_pants_on_fire, with a nicer name of course, propagates some message to the UI. We already have the UI propagation facility in place if I recall correctly.

It would work as it is now with a trial period of 1. However, if the period was configurable we'd need another value trial_period_length to calculate archive > trial_period_length. For now it's fine though.

Do we want to mark the adapter status as "not compliant"? or only post a warning message?

We want "not compliant".

[smarlowucf]

Added archive comparison. Adds error to csp config if archive exists and free trial is still active. In this case the adapter will ignore the free trial flag and bill as normal. The error will be available to products via csp config.

[rjschwei]

Added archive comparison. Adds error to csp config if archive exists and free trial is still active. In this case the adapter will ignore the free trial flag and bill as normal. The error will be available to products via csp config.

Thanks, LGTM