-
Notifications
You must be signed in to change notification settings - Fork 134
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
Payment data sources #34
Conversation
e73d2b2
to
1229614
Compare
hey @gaetanfl Thanks for this PR :) Taking a quick look at this PR it contains sensitive information (IBAN / Credit Card Numbers) which aren't encrypted in the state. Since this is the first time this kind of information has been exposed across providers - we need to chat about this internally before proceeding - please bear with us for the moment and we'll get back to you shortly. Thanks! |
Hi, |
hi @tombuildsstuff & @gaetanfl actually, i'm also checking internally @ovh if this kind of info isnt to sensible to be exposed in a terraform state file. i'm not so sure we want to take this risk. |
hi @gaetanfl i've checked internally. there should be no problem outputting these values as they are returned by the API Do you think we could export only the internal id return by the API if the datasource is found ? |
I guess we could keep for bank account:
and for Credit Card:
Expiration is to check if we shoudl ask account administrator to add another one Will that be ok for you ? |
thanks a lot i think this would be better and avoid us further misunderstandings from end users for expiration date, as it's a credential in a lot forms, couldn't we set a "still_valid_date" filter |
I will just remove it, if someone need it it won't be difficult to implement |
Hi there @gaetanfl - This is looking much better, thanks! Quick question for you since I'm not familiar with this particular OVH API. What is the expected value of the |
@@ -46,6 +46,8 @@ func Provider() terraform.ResourceProvider { | |||
// New naming schema (issue #23) | |||
"ovh_cloud_region": dataSourcePublicCloudRegion(), | |||
"ovh_cloud_regions": dataSourcePublicCloudRegions(), | |||
"ovh_credit_card": dataSourceCreditCard(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we map the ovh api by prefixing datasources by "ovh_me_" ?
pls ? and rename the go functions accordingly ?
thanks a lot
hi @jkohrman |
In order to make payment for vps resource creation or any other kind of classic (non cloud) ovh products a data source for payments method would make things easier.
I've a question regarding tests, if I use two env variable with filter patterns for credit card or bank account and check there is a match, is it enough ?