You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you know you can use a deployment proxy plugin to download and execute an additional blueprint package (ZIP) from for example from Github or any other unauthenticated source. In our case (security measures) we want to use GitLab. But in this case we need to add authentication to the response = requests.get(url, stream=True) line of code in the utils.py (code of deployment proxy). The requests library supports adding these headers.
Can this be seen as a enhancement request to the deployment proxy to support protected blueprint archive URLs ? Like using an API key ? and adding this as a attribute that we can fill-in with a secret.
The text was updated successfully, but these errors were encountered:
@avwsolutions Thanks for the suggestion. This sounds like a very important addition that we should make to the plugin. We will try to add it soon. You are also more than welcome to submit a PR with the code change.
As you know you can use a deployment proxy plugin to download and execute an additional blueprint package (ZIP) from for example from Github or any other unauthenticated source. In our case (security measures) we want to use GitLab. But in this case we need to add authentication to the response = requests.get(url, stream=True) line of code in the utils.py (code of deployment proxy). The requests library supports adding these headers.
Can this be seen as a enhancement request to the deployment proxy to support protected blueprint archive URLs ? Like using an API key ? and adding this as a attribute that we can fill-in with a secret.
The text was updated successfully, but these errors were encountered: