ЯI
1) Как передавать параметры на aws pipeline, в дженкинсе это удобно сделано через groovy параметры, которые подтягивают выбор из списка какого то..
2) как дать разработчку возможность запускать эти пайплайны без доступа в панель aws?
Size: a a a
ЯI
В
E
MM
A
E
A
ES
registry_external_url 'https://registry.******.io'nginx
gitlab_rails['registry_enabled'] = false
gitlab_rails['registry_host'] = 'https://registry.*******.io'
gitlab_rails['registry_path'] = '/var/opt/gitlab/gitlab-rails/shared/registry'
gitlab_rails['registry_api_url'] = 'http://localhost:5050'
registry['enable'] = true
registry['registry_http_addr'] = 'localhost:5050'
registry_nginx['enable'] = true
registry_nginx['listen_port'] = 80
registry_nginx['listen_https'] = false
registry_nginx['proxy_set_headers'] = {
"Host" => "$http_host",
"X-Real-IP" => "$remote_addr",
"X-Forwarded-For" => "$proxy_add_x_forwarded_for",
"X-Forwarded-Proto" => "https",
"X-Forwarded-Ssl" => "on"
}
server {docker-compose
listen 443 http2 ssl;
server_name registry.*********.io;
ssl_certificate /etc/letsencrypt/live/registry.********.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/registry.*******.io/privkey.pem;
location /.well-known {
root /tmp;
}
location / {
proxy_pass http://127.0.0.1:801;
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Ssl on;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_cache off;
proxy_buffering off;
proxy_request_buffering off;
proxy_http_version 1.1;
}
}
server {
listen 80;
server_name registry.********.io;
return 301 https://registry.*********.io$request_uri;
}
ports:
- '801:80'
- '4431:443'
- '221:22'
- '5050:5050'
MT
i
MT
MT
VC
ИА
ИА
S
P