hashicorp / terraform-provider-telefonicaopencloud Goto Github PK

This is a feature which propose to add AK/SK configuration support.

*** background ***

Still now, as the README.md[1] descripted, this provider doesn't support AK/SK authentication. however, in telefonica open cloud has supported AK/SK for a long time.

*** Usecase ***

The tenant admin may generate a temporary AK and SK, then delegate others to maintain the resources via terraform tool with the AK/SK. the admin also can set the available time of the AK/SK. this is a safety way that many users expect.

*** what changes ***

SDK changes
As there are two SDKs in this repos, one is gophercloud which can be able to access to telefonica open cloud services in OpenStack compatible way. another one is huaweicloud/golangsdk which can be able to access to other services that can not be supported by gophercloud. however, gophercloud doesn't have AK/SK feature.

so we have to move all services into huaweicloud/golangsdk. and only use this repository. so that all AK/SK feature will be added into huaweicloud/golangsdk and gophercloud will be removed from this dependencies.

Configuration changes
currently, the configuration of provider already have AK/SK option. but it was only used to access to OBS service. username/password also needed.

after this PR, if has the AK/SK config, the username/password will not work any more. that means the AK/SK has a high priority.

Terraform Version
any

Affected Resource(s)
Please list the resources as a list, for example:
N/A

References
[1]https://github.com/terraform-providers/terraform-provider-telefonicaopencloud#quick-start

As part of the preparation for Terraform v0.12, we would like to migrate all providers to use Go Modules. We plan to continue checking dependencies into vendor/ to remain compatible with existing tooling/CI for a period of time, however go modules will be used for management. Go Modules is the official solution for the go programming language, we understand some providers might not want this change yet, however we encourage providers to begin looking towards the switch as this is how we will be managing all Go projects in the future. Would maintainers please react with 👍 for support, or 👎 if you wish to have this provider omitted from the first wave of pull requests. If your provider is in support, we would ask that you avoid merging any pull requests that mutate the dependencies while the Go Modules PR is open (in fact a total codefreeze would be even more helpful), otherwise we will need to close that PR and re-run go mod init. Once merged, dependencies can be added or updated as follows:

$ GO111MODULE=on go get github.com/some/module@master
$ GO111MODULE=on go mod tidy
$ GO111MODULE=on go mod vendor

GO111MODULE=on might be unnecessary depending on your environment, this example will fetch a module @ master and record it in your project's go.mod and go.sum files. It's a good idea to tidy up afterward and then copy the dependencies into vendor/. To remove dependencies from your project, simply remove all usage from your codebase and run:

$ GO111MODULE=on go mody tidy
$ GO111MODULE=on go mod vendor

Thank you sincerely for all your time, contributions, and cooperation!