feat: Add way to get Configtype time value for hashing #2077
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
First option was using exported fields, but even that would require additional logic- e.g. what should happen, if the user provided input is
50 minutes ago
and the sync is run twice at different times?I think this approach makes more sense, but let me know if there are any other ideas or comments to consider.
closes https://github.com/cloudquery/cloudquery-private/issues/6478