Comments (1)
200sc
commented on August 10, 2024
Unfortunately, the API key pairs that control public API access (and therefore terraform as well) are not currently allowed to posses permissions to connect to or execute commands against resources in StrongDM.
This can be considered as a feature request, but it will be complicated, as it would be unusual for a terraform provider or SDK to assume the existence of and interface with a locally hosted StrongDM listener or client running on the machine executing the terraform job. Additionally, the ability to execute queries against a resource is a permission that opens up billing questions.
If this feature request is still of interest, please reference this issue in a message to [email protected].
from terraform-provider-sdm.
Related Issues (20)
- resource exhausted: Sorry! You've made too many requests, try again HOT 2
- Import example for Secrets Store is incorrect HOT 1
- Example in Data Source documentation for `sdm_resource` is incorrect HOT 1
- Tags option not working for some Data Source filters HOT 1
- cannot read SecretStore: unauthenticated: cannot find auth GUID HOT 1
- Support for mapping sdm_roles with sdm_datasource using "name" as identifier instead of relying on tags or id HOT 5
- Bump the module version to `v2` HOT 1
- add way to set default tags HOT 1
- Split sdm_role resource and use attachments HOT 2
- username is not imported for mongo db resources HOT 3
- Using SDM in module causes terraform to insist on trying to get non-existent "hashicorp/sdm" module
- Add support for default_tags in the SDM Provider HOT 1
- Terraform does not catch username and password changes done on the website HOT 4
- secret_store_id change should force new resource HOT 3
- secret store id change still doesn't force re-creation on all resource types HOT 3
- Fix sdm_resource > google_gke > healthcheck_namespace so that it's not permanently diffed HOT 2
- Add port_override to google_gke resource HOT 2
- Changing a port_override creates a plan that cannot be applied HOT 1
- Changing the `sdm_resource` type doesn't cause a replacement HOT 5
- data sdm_peering_group: small bug? HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-sdm.