You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having to do date math is cumbersome in a shell. While there are versions of date that attempt to make it easier to add 2 hours to now, it's not the most automation-friendly when you might have a different version of date. Or one might try a perl one-liner to manipulate a timestamp.
How could the Equinix Metal CLI help solve this problem?
the addition of a --ttl flag that accepts an int64 for seconds would be far easier to build automation around.
The text was updated successfully, but these errors were encountered:
I was flipping through kong docs as I'm considering how we could benefit from a move from kingpin / viper in this project to kong. Kong appears to support Parse and ParseDuration out of the box for timestamp fields.
For now some documentation about what format it's even expecting would be good. The params aren't even documented here https://metal.equinix.com/developers/api/devices/ so I can't really tell what I'm doing. Is it a UTC time? Is the CLI going to convert it? etc?
What problem are you facing?
Having to do date math is cumbersome in a shell. While there are versions of
date
that attempt to make it easier to add 2 hours tonow
, it's not the most automation-friendly when you might have a different version ofdate
. Or one might try aperl
one-liner to manipulate a timestamp.How could the Equinix Metal CLI help solve this problem?
the addition of a
--ttl
flag that accepts anint64
for seconds would be far easier to build automation around.The text was updated successfully, but these errors were encountered: