Permission validity should be configurable

[mikaelarguedas]

Feature request

Feature description

Generated permissions file should use the same validity period as the certificates.
Currently they use hard coded timeframe that expires in 2023

sros2/sros2/sros2/policy/templates/dds/permissions.xsl

Line 12 in 9e1d105

<not_before>2013-10-26T00:00:00</not_before>

Implementation considerations

Certificates currently use [UTC:UTC+10years]

sros2/sros2/sros2/api/__init__.py

Line 451 in 9e1d105

utcnow = datetime.datetime.utcnow()

The same could be used.

Ideally the user would be able to specify the start date and the dureation. That range would be applied to both the certificates and permissions files

[kyrofa]

The same could be used.

That sounds like a bug, and could be fixed after feature freeze.

Ideally the user would be able to specify the start date and the duration.

Yeah, that's more of a feature.

[hidmic]

@kyrofa @mikaelarguedas are you planning to land said feature for Foxy?

[kyrofa]

It's after feature freeze now, so I suspect we'll go the bugfix route on this one.

[dirk-thomas]

I don't know what this needs to be merged but we haven't frozen yet. It might still be ~ a day out.

[mikaelarguedas]

I won't work on this in the next couple days. I should be able to provide a bugfix to have matching validity dates next week

[mikaelarguedas]

bugfix submitted at #205