Open grahamc opened 3 years ago
Thanks, @grahamc.
The capabilities of the project API keys are definitely inferior to those offered by user API keys. There are some internal tickets to improve their capabilities and the documentation about capability parity.
The logging output could be improved too, I've also experienced the mix of requests and responses. Some request specific identifier log message prefix could be helpful.
@grahamc Were you able to create the SMR with the project API key and then you couldn't fetch the same SMR with that key? Or are you only looking for project API keys to have read access to SMR resources? (I'm wondering if this is a bug report, create but no read, or a feature request for read and write).
This is a general problem with Metal's API and how it handles authentication. However, it shows up in terraform too.
Using a project token, I can't request
https://api.equinix.com/metal/v1/spot-market-requests/*
:As a related issue, the debug log for this provider doesn't print the debug request logs errors in a way which correlates requests to responses. Here is an example:
however this request does work, it is just that the printing happened to interlace two different requests.
Terraform Version
Terraform v0.12.29
with this provider at v1.0.0.Affected Resource(s)
Please list the resources as a list, for example:
metal_spot_market_request
and probably others like SSH keys.
Terraform Configuration Files
Expected Behavior
Project keys should be allowed to manage a project's resources.
Actual Behavior
I get inscrutable error messages:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply