HTTP Proxy Manager Static Config Merge #614
-
What product are you having troubles with?Console What Console version are you using?13.6.2 DescriptionWhen using the static configuration, we are wanting to expose as much of the configuration in the console as possible, e.g. as part of a configMap. However, in practice most (probably all) require a secret to be included in the configuration. This works, but it moves the entire config into our secret management tool, and is not visible in the console. Is it possible to use some sort of JSON merge to allow for partial configuration in the console, while keeping the rest in a secret? This is an example of what might be a complete configuration: "proxies": [
{
"additionalHeaders": [
{
"name": "Authorization",
"value": "Basic fakebasicauthheader="
}
],
"basePath": "/original",
"targetBaseUrl": "http://microservice-b/anything/new"
}
]What we would like in the console is: "proxies": [
{
"additionalHeaders": [
{
"name": "Authorization",
"value": "env.SUPER_SECRET_VARIABLE"
}
],
"basePath": "/original",
"targetBaseUrl": "http://microservice-b/anything/new"
}
]or something similar. The main goal is to have explicit configuration visible in Mia to help users who do not have access to the secret, or just don't need to see what the secret is to perform their task. Actual OutcomeOur entire configuration exists as a secret not visible in the console. Expected OutcomeWe want visibility into as much of the configuration as possible where only actual secret data is stored outside of the console. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Another way that I have thought about tackling this problem is through init containers. Are init containers supported by Mia? Any other thoughts are welcome. |
Beta Was this translation helpful? Give feedback.
This is no longer a blocker since it has been open sourced through https://github.com/mia-platform-marketplace/http-proxy-manager.
Thank you!