Skip to content

Conversation

mdb
Copy link

@mdb mdb commented Apr 21, 2025

This seeks to address issue #34 by offering the ability to specify provider-level host configuration & host-specific request headers.

This also presents as an alternative implementation to PR #521 and PR #12, perhaps a bit more inline with what @apparentlymart recommended a while back.

@mdb mdb force-pushed the mdb/configurable-host branch from 0175420 to acad059 Compare April 21, 2025 21:27
request.Host = header
}
}
}
Copy link
Author

Choose a reason for hiding this comment

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

Callout: ☝️ Ideally (at least for my use case), these provider-level headers are regarded as sensitive and therefore not logged in plain text if/when TF_DEBUG=1, etc. I haven't dug too deep on whether they currently are.

@mdb mdb force-pushed the mdb/configurable-host branch from acad059 to 7cba77c Compare April 21, 2025 21:30
@mdb mdb force-pushed the mdb/configurable-host branch from 7cba77c to 1c2ec85 Compare April 22, 2025 12:27
@mdb mdb marked this pull request as ready for review April 22, 2025 12:27
@mdb mdb requested a review from a team as a code owner April 22, 2025 12:27
@mdb mdb changed the title feat: support provider host configuration feat: support provider-level host configuration Apr 22, 2025
@mdb mdb force-pushed the mdb/configurable-host branch 2 times, most recently from db7d1a5 to 75aa6e5 Compare April 22, 2025 12:54
This seeks to address issue hashicorp#34 by offering the ability to specify
provider-level host configuration & host-specific request headers.

Signed-off-by: Mike Ball <mikedball@gmail.com>
@mdb mdb force-pushed the mdb/configurable-host branch from 75aa6e5 to b217007 Compare April 25, 2025 12:46
@ansgarm
Copy link
Member

ansgarm commented May 12, 2025

Hi @mdb,

Thanks for your PR and for your patience!
We've decided we won't be able to prioritize this feature in the near future. Our focus is elsewhere at this point and this needs more consideration.

I'm sorry if my previous reply came across as too optimistic. We appreciate your contribution and hope you understand our decision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants