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.

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

aws: add support for elasticache resource #68

Merged
merged 12 commits into from
Mar 22, 2022
Merged

aws: add support for elasticache resource #68

merged 12 commits into from
Mar 22, 2022

Conversation

talset
Copy link
Member

@talset talset commented Dec 29, 2021

add support for

  • aws_eip
  • aws_aws_elasticache_cluster
  • aws_elasticache_replication_group

@talset talset force-pushed the aws-elasticache branch 3 times, most recently from 5471097 to baec2e1 Compare December 29, 2021 15:30
@talset talset force-pushed the aws-elasticache branch 5 times, most recently from 6a029f9 to f5212c5 Compare January 7, 2022 16:37
@talset talset force-pushed the aws-elasticache branch 4 times, most recently from 1c6aff6 to ea87064 Compare January 13, 2022 17:01
To match CSV column and variable, rename:
 * PurchaseOption to PurchaseOption
 * TermPurchaseOption to TermType
 * startUsageAmount to startingRange
@talset talset force-pushed the aws-elasticache branch 2 times, most recently from a51ce54 to e59d32b Compare February 2, 2022 12:41
@talset talset marked this pull request as ready for review February 2, 2022 12:48
@talset talset added enhancement New feature or request need review labels Feb 2, 2022
@talset talset force-pushed the aws-elasticache branch 2 times, most recently from 79d17df to eaffe6d Compare February 2, 2022 18:25
talset added 4 commits March 15, 2022 16:03
To keep consistency between CSV value and query from resource
implementation. Ingester will keep the same value from the CSV to
the DB.
it impact previous key/column names and on_demand/reserved value which actually is OnDemand and Reserved
from the CSV.

Column name will be change with field variable name when ingesting in
the DB.
Basically it is the name without spacies.
Even if json accept space in key names, we choose to remove them for
simplification reason.
Take care of the res.PriorCost() and res.PlannedCost() 2 returns.
Copy link
Member

@xescugc xescugc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say LGTM but it's missing the changelog

@talset talset requested a review from xescugc March 22, 2022 10:18
@talset talset merged commit ddec684 into master Mar 22, 2022
@talset talset deleted the aws-elasticache branch March 22, 2022 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request need review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants