Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deprecate expiration_epoch for Tombstone? #215

Closed
carpawell opened this issue Apr 19, 2022 · 0 comments
Closed

Deprecate expiration_epoch for Tombstone? #215

carpawell opened this issue Apr 19, 2022 · 0 comments
Assignees
@cthulhu-rider
Labels
I3 Minimal impact question Further information is requested S3 Minimally significant U4 Nothing urgent
Milestone
v2.16.0

Comments

@carpawell
Copy link
Member

The same way as it was suggested in #205. No need to get a payload for tombstone expiration, also, I did not find any example of body field usage in the node.
@carpawell carpawell added question Further information is requested triage labels Apr 19, 2022
@roman-khimov roman-khimov added U4 Nothing urgent S3 Minimally significant I3 Minimal impact and removed triage labels Dec 20, 2023
@cthulhu-rider cthulhu-rider self-assigned this Feb 26, 2024
cthulhu-rider added a commit that referenced this issue Feb 26, 2024
@cthulhu-rider
tombstone: Mark expiration_epoch field as deprecated
4199b40 
There is no need to transfer data that's already set in other place and
require equality.

Closes #215.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
cthulhu-rider added a commit that referenced this issue Feb 26, 2024
@cthulhu-rider
tombstone: Mark expiration_epoch field as deprecated
610d95e 
There is no need to transfer data that's already set in other place and
require equality.

Closes #215.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
cthulhu-rider added a commit that referenced this issue Feb 27, 2024
@cthulhu-rider
tombstone: Mark expiration_epoch field as deprecated
105a02c 
There is no need to transfer data that's already set in other place and
require equality.

Closes #215.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
cthulhu-rider added a commit that referenced this issue Feb 27, 2024
@cthulhu-rider
tombstone: Mark expiration_epoch field as deprecated
109d50d 
There is no need to transfer data that's already set in other place and
require equality.

Closes #215.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
@roman-khimov roman-khimov added this to the v2.16.0 milestone Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cthulhu-rider cthulhu-rider

Labels
I3 Minimal impact question Further information is requested S3 Minimally significant U4 Nothing urgent
Projects
None yet
Milestone
v2.16.0
Development

No branches or pull requests
3 participants
@roman-khimov @carpawell @cthulhu-rider